[
https://issues.apache.org/jira/browse/HBASE-27394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17610067#comment-17610067
]
Bryan Beaudreault commented on HBASE-27394:
-------------------------------------------
According to your comment on the DISCUSS thread related to this change,
log4j.properties should work:
[https://lists.apache.org/thread/0hr22ndxxqq3rj2360k0t8c2o09wf65k]. It also
seemed to be a goal of the backport jira:
https://issues.apache.org/jira/browse/HBASE-26802
That said, I realized this was a problem with our deploy. We were pulling in
both log4j (from hadoop) and log4j2 jars on the regionserver classpath.
Cleaning all of that up and indeed the log4j.properties stops working and the
servlet starts work. Seems like this is not a bug, will resolve.
> 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)
