[
https://issues.apache.org/jira/browse/AMBARI-20390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904969#comment-15904969
]
Hadoop QA commented on AMBARI-20390:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12857159/screenshot-1.png
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10963//console
This message is automatically generated.
> 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
> Fix For: trunk
>
> 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)
