ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "WangJie (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-20390) Inappropriate kafka log4j configuration results in too much kafka logs
Date Fri, 10 Mar 2017 02:08:38 GMT

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

WangJie updated AMBARI-20390:
-----------------------------
    Status: Patch Available  (was: Open)

> 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, screenshot-1.png
>
>
> 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)

Mime
View raw message