You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Ashutosh Gupta (Jira)" <ji...@apache.org> on 2022/07/06 21:07:00 UTC
[jira] [Commented] (YARN-9342) Moving log4j1 to log4j2 in hadoop-yarn
[ https://issues.apache.org/jira/browse/YARN-9342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17563428#comment-17563428 ]
Ashutosh Gupta commented on YARN-9342:
--------------------------------------
Hi [~abmodi] - Can you please some info about the process that you guys opted for switching to Log4j2 ? It will be really helpful.
> Moving log4j1 to log4j2 in hadoop-yarn
> --------------------------------------
>
> Key: YARN-9342
> URL: https://issues.apache.org/jira/browse/YARN-9342
> Project: Hadoop YARN
> Issue Type: Improvement
> Affects Versions: 3.1.2
> Reporter: Prabhu Joseph
> Assignee: Prabhu Joseph
> Priority: Major
>
> 1. Log4j2 Asynchronous Logging will give significant improvement in the performance.
> 2. Log4j2 does not have below locking issue which Log4j1 has.
> {code}
> "Thread-16" #40 daemon prio=5 os_prio=0 tid=0x00007f181f9bb800 nid=0x125 waiting for monitor entry [0x00007ef163bab000]
> java.lang.Thread.State: BLOCKED (on object monitor)
> at org.apache.log4j.Category.callAppenders(Category.java:204)
> - locked <0x00007ef2d803e2b8> (a org.apache.log4j.spi.RootLogger)
> at org.apache.log4j.Category.forcedLog(Category.java:391)
> at org.apache.log4j.Category.log(Category.java:856)
> at org.apache.commons.logging.impl.Log4JLogger.info(Log4JLogger.java:176)
> {code}
> https://bz.apache.org/bugzilla/show_bug.cgi?id=57714
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org