[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 ] Jayush Luniya updated AMBARI-20390: --- Resolution: Not A Problem Status: Resolved (was: Patch Available) > 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 >Assignee: Jayush Luniya >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)
[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: - Affects Version/s: (was: 2.4.0) 2.7.2 2.7.1 2.7.0 > 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: 50m > 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)
[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 ] ASF GitHub Bot updated AMBARI-20390: Labels: pull-request-available (was: ) > 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.4.0 >Reporter: WangJie >Priority: Major > Labels: pull-request-available > 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 (v7.6.3#76005)
[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 ] Doroszlai, Attila updated AMBARI-20390: --- Component/s: (was: ambari-sever) ambari-server > 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.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)
[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: - Fix Version/s: trunk > 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)
[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: - 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)
[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: screenshot-1.png > 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)
[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)