You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "WangJie (JIRA)" <ji...@apache.org> on 2017/03/10 02:05:37 UTC

[jira] [Updated] (AMBARI-20390) Inappropriate kafka log4j configuration results in too much kafka logs

     [ https://issues.apache.org/jira/browse/AMBARI-20390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

WangJie updated AMBARI-20390:
-----------------------------
    Attachment: AMBARI-20390.patch

> Inappropriate kafka log4j configuration results in too much kafka logs 
> -----------------------------------------------------------------------
>
>                 Key: AMBARI-20390
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20390
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-sever
>    Affects Versions: trunk, 2.4.0
>            Reporter: WangJie
>         Attachments: AMBARI-20390.patch
>
>
> Inappropriate kafka log4j configuration results in too much kafka logs which are constantly increasing and never be removed.
> Besides,DailyRollingFileAppender does not support property:maxBackupIndex and maxFileSize, Only RollingFileAppender supports it.
> Suggestion:
> Change kafka log4j appender mode from DailyRollingFileAppender to RollingFileAppender.
> In this way, it will automatically remove the useless kafka log file.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)