[jira] [Updated] (KAFKA-429) Expose JMX operation to set logger level dynamically

["Joel Koshy (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joel Koshy updated KAFKA-429:
-----------------------------

    Attachment: KAFKA-429-trunk-v1.patch
                KAFKA-429-0.8-v1.patch

Patch for 0.8 and trunk.

This adds a new log4j controller mbean that allows getting/setting log4j levels dynamically.

The logging trait forces initialization of the companion object. This means tools such as console consumer and mirror maker get the mbean automatically (since most of the tools use the logging trait).

Also, I removed the older LoggerDynamicMbean which is superseded by the new mbean.

Finally (unrelated): log the throwable on producer send exception.

                
> Expose JMX operation to set logger level dynamically
> ----------------------------------------------------
>
>                 Key: KAFKA-429
>                 URL: https://issues.apache.org/jira/browse/KAFKA-429
>             Project: Kafka
>          Issue Type: New Feature
>          Components: core
>    Affects Versions: 0.8, 0.7.2
>            Reporter: Joel Koshy
>         Attachments: KAFKA-429-0.8-v1.patch, KAFKA-429-trunk-v1.patch
>
>
> With KAFKA-16, we can change logger levels dynamically, but that is a global setting - i.e., it affects logging in all classes. It would be useful to expose a setLoggerLevel/add appenders operation that can be applied to classes/packages.
> We should also add this for the tools (and not just the broker) - e.g., mirror-maker, console consumer, etc.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira