[RELEASE] Ingest - Remove conflicting logging provider AND Decrease consumer threads

[mreyescdl]

Overview of Release

Controlling Zookeeper logging messages with logback has varying results. On stage it works however on prod it does not. Cause is due to the random nature in which SLF4J decides which logging provider is chosen if multiple exist. Here is the message in production

SLF4J(W): Class path contains multiple SLF4J providers.
SLF4J(W): Found provider [org.slf4j.simple.SimpleServiceProvider@6ac4da08]
SLF4J(W): Found provider [ch.qos.logback.classic.spi.LogbackServiceProvider@140fb15a]
SLF4J(W): See https://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J(I): Actual provider is of type [org.slf4j.simple.SimpleServiceProvider@6ac4da08]

By removing the SimpleServiceProvider, there is no decision to make. Logback is chosen and ZK logging is controlled. This is implemented by simply remove the following in the pom.xml

<dependency>
    <groupId>org.slf4j</groupId>
    <artifactId>slf4j-simple</artifactId>
</dependency>

Also included in this release is to decrease Consumer threads from 3 to 2. This addresses overtaxing of Storage issue.

Service(s)

Ingest

Github Issue Link(s)

https://github.com/CDLUC3/mrt-doc/issues/2026

Servers affected

uc3-mrtingest-prd01,uc3-mrtingest-prd02,uc3-mrtingest-prd03

Source Code:

(insert pull request here)

Source Code Tag

2.1.5

Jenkins/Build Info: (if applicable)

N/A

Deployment Steps (if applicable)

• [ ] Use ansible deployment

Infrastructure Changes to support deployment (ALB, EFS, etc)

N/A - controlled through Ansible

Rollback Instructions

• controlled through ansible

[mreyescdl]

Deployed. Integration test passes. Nice to have the Ingest logs cleared of the ZK white noise

[elopatin-uc3]

Thanks @mreyescdl !