[HBASE-29000] SLF4j logging backend incorrectly picked up from Hadoop when external Hadoop is specified

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-beta-1, 2.7.0, 2.6.1, 2.5.10
• Fix Version/s: 2.7.0, 3.0.0-beta-2, 2.5.11, 2.6.2
• Component/s: logging, scripts
• Labels: pull-request-available
• Assignee: Istvan Toth
• Reporter: Istvan Toth
• Created: 27/Nov/24 12:20
• Updated: 03/Dec/24 12:25
• Resolved: 28/Nov/24 08:46

Description

When I set  HADOOP_CLASSPATH:

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/stoty/x/hadoop-3.4.1/share/hadoop/common/lib/slf4j-reload4j-1.7.36.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/stoty/workspaces/hbase/hbase/hbase-assembly/target/hbase-2.5.11-SNAPSHOT-client/lib/client-facing-thirdparty/log4j-slf4j-impl-2.17.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Reload4jLoggerFactory]

HBase should always pick its own log4j2 backend.

Issue Links

• is depended upon by: HBASE-28434 Update assembly to create a tarball with hadoop and without hadoop
• links to: GitHub Pull Request #6495
• links to: GitHub Pull Request #6497