[
https://issues.apache.org/jira/browse/HBASE-26802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-26802:
------------------------------
Release Note:
Use log4j2 instead of log4j for logging.
Exclude log4j dependency from hbase and transitive dependencies, use
log4j-1.2-api as test dependency for bridging as hadoop still need log4j for
some reasons. Copy FileAppender implementation in hbase-logging as the
ContainerLogAppender for YARN NodeManager extends it. All log4j.properties
files have been replaced by log4j2.properties.
was:
Use log4j2 instead of log4j for logging.
Exclude log4j dependency from hbase and transitive dependencies, use
log4j-1.2-api as test dependency for bridging as hadoop still need log4j for
some reasons. Copy FileAppender implementation in hbase-logging as the
ContainerLogAppender for YARN NodeManager extends it. All log4j.properties
files have been replaced by log4j2.xml.
For log4j2, there is no 'log4j.rootLogger' config, so we need to config level
and appender separately, the system properties are now
'hbase.root.logger.level' and 'hbase.root.logger.appender', for security
loggers they are 'hbase.security.logger.level' and
'hbase.security.logger.appender'. But for setting them from command line, you
could still use something like 'HBASE_ROOT_LOGGER=INFO,console' as we will
split it and set level and appender separately.
> Backport the log4j2 changes to branch-2
> ---------------------------------------
>
> Key: HBASE-26802
> URL: https://issues.apache.org/jira/browse/HBASE-26802
> Project: HBase
> Issue Type: Task
> Components: logging
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Blocker
> Fix For: 2.5.0, 2.6.0
>
>
> One thing is that, we'd better make sure that users can still use the old
> log4j.properties for logging.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
