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 2022/09/27 12:57:00 UTC

[jira] [Commented] (HBASE-27394) LogLevel.Servlet not working in 2.5.0

    [ https://issues.apache.org/jira/browse/HBASE-27394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17610039#comment-17610039 ] 

Duo Zhang commented on HBASE-27394:
-----------------------------------

2.5.0 uses log4j2 so I do not think log4j.properties could take effect, as the format of the configuration file is completely different...

> LogLevel.Servlet not working in 2.5.0
> -------------------------------------
>
>                 Key: HBASE-27394
>                 URL: https://issues.apache.org/jira/browse/HBASE-27394
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 2.5.0
>            Reporter: Bryan Beaudreault
>            Priority: Major
>
> I'm upgrading our servers to hbase 2.5.0 and noticed that the LogLevel.Servlet no longer works. I am guessing this is due to the log4j2 change.
> According to the servlet output, it sees log class as {{org.slf4j.impl.Log4jLoggerAdapter}} but the log levels seem totally disconnected from reality — setting a log level has no effect, and checking the loglevel of a logger that i had configured in my log4j.properties shows the wrong value. Logging itself seems to be using my log4j.properties correctly, but the LogLevel.Servlet sees and sets a different view
> I tried moving aside the {{log4j2.properties}} and also separately tried moving aside the {{{}log4j.properties{}}}, neither helped



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