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

["Duo Zhang (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-27244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Duo Zhang resolved HBASE-27244.
-------------------------------
    Fix Version/s: 2.4.14
     Hadoop Flags: Reviewed
       Resolution: Fixed

Merged to branch-2.4+.

Thanks [~Li0829] for contributing!

> bin/hbase still use slf4j-log4j while reload4j in place
> -------------------------------------------------------
>
>                 Key: HBASE-27244
>                 URL: https://issues.apache.org/jira/browse/HBASE-27244
>             Project: HBase
>          Issue Type: Bug
>          Components: shell
>    Affects Versions: 2.4.13
>            Reporter: Dong0829
>            Assignee: Dong0829
>            Priority: Major
>             Fix For: 2.4.14
>
>
> 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 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)