-
Notifications
You must be signed in to change notification settings - Fork 9.1k
HADOOP-18649. CLA and CRLA appenders to be replaced with RFA #5448
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
@Apache9 @jojochuang could you please review this PR? |
...oop-yarn-server/hadoop-yarn-server-nodemanager/src/main/resources/container-log4j.properties
Show resolved
Hide resolved
...oop-yarn-server/hadoop-yarn-server-nodemanager/src/main/resources/container-log4j.properties
Show resolved
Hide resolved
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
I just checked usages with https://github.com/search?l=Java+Properties&q=org%3Aapache+org.apache.hadoop.yarn.ContainerRollingLogAppender&type=Code Looks like only yarn has the references. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM merging it.
…pache#5448)" This reverts commit cf4a678.
ContainerLogAppender and ContainerRollingLogAppender both have quite similar functionality as RollingFileAppender. Maintenance of custom appenders for Log4J2 is costly when there is very minor difference in comparison with built-in appender provided by Log4J.
The goal of this sub-task is to replace both ContainerLogAppender and ContainerRollingLogAppender custom appenders with RollingFileAppender without changing any system properties already being used to determine file name, file size, backup index, pattern layout properties etc.