[HBASE-27244] bin/hbase still use slf4j-log4j while reload4j in place

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.13
• Fix Version/s: 2.4.14
• Component/s: shell
• Hadoop Flags: Reviewed
• Assignee: Dong0829
• Reporter: Dong0829
• Created: 27/Jul/22 00:54
• Updated: 11/Aug/22 00:06
• Resolved: 10/Aug/22 08:14

Description

For the bin/hbase file, there are some class path set which will handle the slf4j-log4j before, but now in hbase branch 2, we upgrade to reload4j, but the hbase file not upgrade, for example, if we run mapredcp:

hbase mapredcp:

/usr/lib/hbase/lib/shaded-clients/hbase-shaded-mapreduce-2.4.12.jar:/usr/lib/hbase/lib/client-facing-thirdparty/audience-annotations-0.5.0.jar:/usr/lib/hbase/lib/client-facing-thirdparty/commons-logging-1.2.jar:/usr/lib/hbase/lib/client-facing-thirdparty/htrace-core4-4.2.0-incubating.jar:/usr/lib/hbase/lib/client-facing-thirdparty/jcl-over-slf4j-1.7.33.jar:/usr/lib/hbase/lib/client-facing-thirdparty/jul-to-slf4j-1.7.33.jar:/usr/lib/hbase/lib/client-facing-thirdparty/reload4j-1.2.19.jar:/usr/lib/hbase/lib/client-facing-thirdparty/slf4j-api-1.7.33.jar:/usr/lib/hbase/lib/client-facing-thirdparty/slf4j-reload4j-1.7.33.jar

Among above, /usr/lib/hbase/lib/client-facing-thirdparty/slf4j-reload4j-1.7.33.jar should be excluded but as slf4j-log4j before

This will impact the downstream users

Issue Links

• links to: GitHub Pull Request #4652