[jira] [Commented] (HBASE-27244) bin/hbase still use slf4j-log4j while reload4j in place
[
https://issues.apache.org/jira/browse/HBASE-27244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17578186#comment-17578186
]
Hudson commented on HBASE-27244:
Results for branch branch-2.4
[build #407 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/407/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/407/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/407/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/407/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/407/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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)
[jira] [Commented] (HBASE-27244) bin/hbase still use slf4j-log4j while reload4j in place
[ https://issues.apache.org/jira/browse/HBASE-27244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17571683#comment-17571683 ] Dong0829 commented on HBASE-27244: -- Yes, I am preparing the PR > 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 >Priority: Major > > 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)
[jira] [Commented] (HBASE-27244) bin/hbase still use slf4j-log4j while reload4j in place
[ https://issues.apache.org/jira/browse/HBASE-27244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17571682#comment-17571682 ] Duo Zhang commented on HBASE-27244: --- Mind opening a PR to fix it? > 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 >Priority: Major > > 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)
