[jira] [Commented] (KAFKA-6852) Allow Log Levels to be dynamically configured
[ https://issues.apache.org/jira/browse/KAFKA-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16841574#comment-16841574 ] Addison commented on KAFKA-6852: Very true. Because KAFKA-7800 is linked to the KIP can we close this one out as a duplicate? > Allow Log Levels to be dynamically configured > - > > Key: KAFKA-6852 > URL: https://issues.apache.org/jira/browse/KAFKA-6852 > Project: Kafka > Issue Type: Improvement > Components: core >Affects Versions: 1.0.1 >Reporter: Yeva Byzek >Priority: Major > Labels: supportability, usability > > For operational workflows like troubleshooting, it is useful to change log > levels to get more information. > The current two ways to change log levels is painful: > 1. Changing logging level configuration requires restarting processes. > Challenge: service disruption > 2. Can be also done through JMX MBean. Challenge: for the most part > customers don't have JMX exposed to the operators. It exists as PURELY a way > to get stats. > This jira is to make logging level changes dynamic without service restart > and without JMX interface. > This needs to be done in all Kafka components -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KAFKA-6852) Allow Log Levels to be dynamically configured
[ https://issues.apache.org/jira/browse/KAFKA-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16841560#comment-16841560 ] Yeva Byzek commented on KAFKA-6852: --- [~ahuddy] Technically speaking, KAFKA-7800 is a dupe of this one, but as long as it gets fixed :) > Allow Log Levels to be dynamically configured > - > > Key: KAFKA-6852 > URL: https://issues.apache.org/jira/browse/KAFKA-6852 > Project: Kafka > Issue Type: Improvement > Components: core >Affects Versions: 1.0.1 >Reporter: Yeva Byzek >Priority: Major > Labels: supportability, usability > > For operational workflows like troubleshooting, it is useful to change log > levels to get more information. > The current two ways to change log levels is painful: > 1. Changing logging level configuration requires restarting processes. > Challenge: service disruption > 2. Can be also done through JMX MBean. Challenge: for the most part > customers don't have JMX exposed to the operators. It exists as PURELY a way > to get stats. > This jira is to make logging level changes dynamic without service restart > and without JMX interface. > This needs to be done in all Kafka components -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KAFKA-6852) Allow Log Levels to be dynamically configured
[ https://issues.apache.org/jira/browse/KAFKA-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16841555#comment-16841555 ] Addison commented on KAFKA-6852: [~yevabyzek] I think this is a duplicate of https://issues.apache.org/jira/browse/KAFKA-7800 > Allow Log Levels to be dynamically configured > - > > Key: KAFKA-6852 > URL: https://issues.apache.org/jira/browse/KAFKA-6852 > Project: Kafka > Issue Type: Improvement > Components: core >Affects Versions: 1.0.1 >Reporter: Yeva Byzek >Priority: Major > Labels: supportability, usability > > For operational workflows like troubleshooting, it is useful to change log > levels to get more information. > The current two ways to change log levels is painful: > 1. Changing logging level configuration requires restarting processes. > Challenge: service disruption > 2. Can be also done through JMX MBean. Challenge: for the most part > customers don't have JMX exposed to the operators. It exists as PURELY a way > to get stats. > This jira is to make logging level changes dynamic without service restart > and without JMX interface. > This needs to be done in all Kafka components -- This message was sent by Atlassian JIRA (v7.6.3#76005)
