[YARN-9342] Moving log4j1 to log4j2 in hadoop-yarn

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.1.2
• Assignee: Prabhu Joseph
• Reporter: Prabhu Joseph
• Created: 04/Mar/19 05:08
• Updated: 06/Jul/22 21:06

Description

1. Log4j2 Asynchronous Logging will give significant improvement in the performance.

2. Log4j2 does not have below locking issue which Log4j1 has.

"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)

https://bz.apache.org/bugzilla/show_bug.cgi?id=57714

Issue Links

• relates to: HADOOP-12956 Inevitable Log4j2 migration via slf4j