Major Description
Log4j2 has substantial overhead with the default configuration. We found more than 20%~30% OM overhead in a microbenchmark (in which clients sends lookupFile calls) was spent on audit logging, even though we use async audit logger.
Note that while the log4j2 documentation states the location information is disabled by default, we found that explicitly disabling location information has visible performance improvement.
Solution:
add rootLogger.includeLocation=false to OM's audit logger property (om-audit-log4j2.properties file)
After this change, the audit logger overhead reduced to 7%
According to LOG4J2-2644, log4j2 2.12.1 and above improved this. So Ozone 1.1 should be in much better shape. File this Jira for future reference. Maybe it'll benefit other projects that use older Log4j2.
Credit: adoroszlai for identifying the solution.
Details on log4j2 location information: https://logging.apache.org/log4j/2.x/manual/layouts.html#LocationInformation
Attachments
Attachments
Issue Links
- links to