You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Yingda Chen (JIRA)" <ji...@apache.org> on 2018/10/17 03:25:00 UTC
[jira] [Commented] (TEZ-2222) Investigate moving to log4j2 for
logging
[ https://issues.apache.org/jira/browse/TEZ-2222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652896#comment-16652896 ]
Yingda Chen commented on TEZ-2222:
----------------------------------
I am wondering if this is still being considered? log4j2 provides quite some improvement on both performance and memory usage reduction. Both are critical for running large-scale job on Tez
[https://logging.apache.org/log4j/2.x/performance.html]
[https://logging.apache.org/log4j/2.x/manual/garbagefree.html]
> Investigate moving to log4j2 for logging
> ----------------------------------------
>
> Key: TEZ-2222
> URL: https://issues.apache.org/jira/browse/TEZ-2222
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Siddharth Seth
> Priority: Blocker
>
> Via slf4j.
> Some bits to keep in mind
> - We have explicit code which rotates logs using direct log4j12 APIs. This should keep working. I believe the log4j2 APIs are different here
> - API compatibility between log4j12 / log4j2 can be problematic - if both end up on the classpath (I believe the APIs are different)
> - Hadoop dist includes a slf4j-log4j12 binding. Changing the default can result in sl4j-log4j12 and slf4j-log4j2 to co-exist by default - which could be problematic. Needs investigation.
> End of the day, we will likely need an option to use either of the two.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)