[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-20434) Enhance Kafka Service Check
[ https://issues.apache.org/jira/browse/AMBARI-20434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WangJie updated AMBARI-20434: - Resolution: Fixed Status: Resolved (was: Patch Available) > Enhance Kafka Service Check > --- > > Key: AMBARI-20434 > URL: https://issues.apache.org/jira/browse/AMBARI-20434 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: WangJie >Assignee: Dmitry Lysnichenko > Fix For: trunk > > Attachments: AMBARI-20434-1.patch, AMBARI-20434.patch > > > Problem: > Kafka Service Check will create the kafka topic only if the topic doesn't > exist. > if it exists, Kafka Service Check will return success directly. > After topic is being created, we sense that each time running service check > will not reflect the kafka actual state correctly > Suggestion: > Every running kafka service check, delete the existed topic and recreate it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20434) Enhance Kafka Service Check
[ https://issues.apache.org/jira/browse/AMBARI-20434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WangJie updated AMBARI-20434: - Attachment: AMBARI-20434-1.patch > Enhance Kafka Service Check > --- > > Key: AMBARI-20434 > URL: https://issues.apache.org/jira/browse/AMBARI-20434 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: WangJie >Assignee: Dmitry Lysnichenko > Fix For: trunk > > Attachments: AMBARI-20434-1.patch, AMBARI-20434.patch > > > Problem: > Kafka Service Check will create the kafka topic only if the topic doesn't > exist. > if it exists, Kafka Service Check will return success directly. > After topic is being created, we sense that each time running service check > will not reflect the kafka actual state correctly > Suggestion: > Every running kafka service check, delete the existed topic and recreate it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20434) Enhance Kafka Service Check
[ https://issues.apache.org/jira/browse/AMBARI-20434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WangJie updated AMBARI-20434: - Status: Patch Available (was: Open) > Enhance Kafka Service Check > --- > > Key: AMBARI-20434 > URL: https://issues.apache.org/jira/browse/AMBARI-20434 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: WangJie > Fix For: trunk > > Attachments: AMBARI-20434.patch > > > Problem: > Kafka Service Check will create the kafka topic only if the topic doesn't > exist. > if it exists, Kafka Service Check will return success directly. > After topic is being created, we sense that each time running service check > will not reflect the kafka actual state correctly > Suggestion: > Every running kafka service check, delete the existed topic and recreate it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20434) Enhance Kafka Service Check
[ https://issues.apache.org/jira/browse/AMBARI-20434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WangJie updated AMBARI-20434: - Attachment: AMBARI-20434.patch > Enhance Kafka Service Check > --- > > Key: AMBARI-20434 > URL: https://issues.apache.org/jira/browse/AMBARI-20434 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: WangJie > Fix For: trunk > > Attachments: AMBARI-20434.patch > > > Problem: > Kafka Service Check will create the kafka topic only if the topic doesn't > exist. > if it exists, Kafka Service Check will return success directly. > After topic is being created, we sense that each time running service check > will not reflect the kafka actual state correctly > Suggestion: > Every running kafka service check, delete the existed topic and recreate it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20434) Enhance Kafka Service Check
WangJie created AMBARI-20434: Summary: Enhance Kafka Service Check Key: AMBARI-20434 URL: https://issues.apache.org/jira/browse/AMBARI-20434 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk Reporter: WangJie Fix For: trunk Problem: Kafka Service Check will create the kafka topic only if the topic doesn't exist. if it exists, Kafka Service Check will return success directly. After topic is being created, we sense that each time running service check will not reflect the kafka actual state correctly Suggestion: Every running kafka service check, delete the existed topic and recreate it. -- 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)
[jira] [Created] (AMBARI-20390) Inappropriate kafka log4j configuration results in too much kafka logs
WangJie created AMBARI-20390: Summary: 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 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-19998) Unable to stop service when master components is down
[ https://issues.apache.org/jira/browse/AMBARI-19998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WangJie updated AMBARI-19998: - Description: Unable to stop service when master component is down (was: Unable to stop service when master components is down) > Unable to stop service when master components is down > - > > Key: AMBARI-19998 > URL: https://issues.apache.org/jira/browse/AMBARI-19998 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: WangJie > Fix For: trunk > > Attachments: AMBARI-19998.patch, AMBARI-19998.png > > > Unable to stop service when master component is down -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19998) Unable to stop service when master components is down
[ https://issues.apache.org/jira/browse/AMBARI-19998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WangJie updated AMBARI-19998: - Attachment: AMBARI-19998.patch > Unable to stop service when master components is down > - > > Key: AMBARI-19998 > URL: https://issues.apache.org/jira/browse/AMBARI-19998 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: WangJie > Fix For: trunk > > Attachments: AMBARI-19998.patch, AMBARI-19998.png > > > Unable to stop service when master components is down -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19998) Unable to stop service when master components is down
[ https://issues.apache.org/jira/browse/AMBARI-19998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WangJie updated AMBARI-19998: - Status: Patch Available (was: Open) > Unable to stop service when master components is down > - > > Key: AMBARI-19998 > URL: https://issues.apache.org/jira/browse/AMBARI-19998 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: WangJie > Fix For: trunk > > Attachments: AMBARI-19998.patch, AMBARI-19998.png > > > Unable to stop service when master components is down -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19998) Unable to stop service when master components is down
[ https://issues.apache.org/jira/browse/AMBARI-19998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WangJie updated AMBARI-19998: - Attachment: AMBARI-19998.png > Unable to stop service when master components is down > - > > Key: AMBARI-19998 > URL: https://issues.apache.org/jira/browse/AMBARI-19998 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk >Reporter: WangJie > Fix For: trunk > > Attachments: AMBARI-19998.png > > > Unable to stop service when master components is down -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19998) Unable to stop service when master components is down
WangJie created AMBARI-19998: Summary: Unable to stop service when master components is down Key: AMBARI-19998 URL: https://issues.apache.org/jira/browse/AMBARI-19998 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: trunk Reporter: WangJie Fix For: trunk Unable to stop service when master components is down -- This message was sent by Atlassian JIRA (v6.3.15#6346)
