You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2023/06/06 09:50:00 UTC
[jira] [Commented] (HBASE-27911) log4j configuration file not worked
[ https://issues.apache.org/jira/browse/HBASE-27911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17729676#comment-17729676 ]
Duo Zhang commented on HBASE-27911:
-----------------------------------
What do you mean by can not enable debug by modifying the log4j configurations?
This is what we have in log4j2.properties
{noformat}
rootLogger = ${sys:hbase.root.logger:-INFO,console}
{noformat}
If you change this to
{noformat}
rootLogger = DEBUG,console
{noformat}
You can get what you want as it will not read the system properties any more.
Which HBase do you on? Maybe this is a problem in the log4j1 configuration file?
Thanks.
> 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)