[ 
https://issues.apache.org/jira/browse/HADOOP-18649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695519#comment-17695519
 ] 

ASF GitHub Bot commented on HADOOP-18649:
-----------------------------------------

virajjasani opened a new pull request, #5448:
URL: https://github.com/apache/hadoop/pull/5448

   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.




> CLA and CRLA appenders to be replaced with RFA
> ----------------------------------------------
>
>                 Key: HADOOP-18649
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18649
>             Project: Hadoop Common
>          Issue Type: Sub-task
>            Reporter: Viraj Jasani
>            Assignee: Viraj Jasani
>            Priority: Major
>
> 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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to