[
https://issues.apache.org/jira/browse/HBASE-27911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17730340#comment-17730340
]
caijialiang commented on HBASE-27911:
-------------------------------------
[~zhangduo]
Thank you very much for your attention. The version of hbase I am using is
2.4.13, and this is indeed an issue with log4j1. Since the new version has
fixed the issue, I will close this issue.
> log4j configuration file not worked
> -----------------------------------
>
> Key: HBASE-27911
> URL: https://issues.apache.org/jira/browse/HBASE-27911
> Project: HBase
> Issue Type: Bug
> Reporter: caijialiang
> Priority: Major
>
> HBase sets the HBASE_ROOT_LOGGER variable in many startup scripts, and
> finally places this variable in the startup parameters in the bin/hbase
> script, "-Dhbase.root.logger=${HBASE_ROOT_LOGGER:-INFO,console}". This is
> really strange as it overrides the log4j configuration, which is not
> beneficial for users who are not familiar with HBase because they cannot
> enable debug by modifying the log4j configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
