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

["Jayush Luniya (JIRA)" <ji...@apache.org>]

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

Jayush Luniya commented on AMBARI-20390:
----------------------------------------

The configs defined in the stack definitions are only the default values and can be changed by the end user when deploying the cluster. You can change the log4j properties from the UI without having to change the default.


> 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-server
>    Affects Versions: trunk, 2.7.0, 2.7.1, 2.7.2
>            Reporter: WangJie
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: trunk
>
>         Attachments: AMBARI-20390.patch, screenshot-1.png
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> 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
(v7.6.3#76005)