[
https://issues.apache.org/jira/browse/FLUME-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13736235#comment-13736235
]
Hudson commented on FLUME-2156:
-------------------------------
SUCCESS: Integrated in flume-trunk #490 (See
[https://builds.apache.org/job/flume-trunk/490/])
FLUME-2156. Unregister then re-register MonitoredCounterGroup JMX MBeans on
reconfigure (hshreedharan:
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=507ff137160021dda2c4a08199746228827c9432)
*
flume-ng-core/src/test/java/org/apache/flume/instrumentation/TestMonitoredCounterGroup.java
*
flume-ng-core/src/main/java/org/apache/flume/instrumentation/MonitoredCounterGroup.java
> Unregister then re-register MonitoredCounterGroup JMX MBeans on reconfigure
> ---------------------------------------------------------------------------
>
> Key: FLUME-2156
> URL: https://issues.apache.org/jira/browse/FLUME-2156
> Project: Flume
> Issue Type: Bug
> Affects Versions: v1.4.0
> Reporter: Mike Percy
> Assignee: Mike Percy
> Fix For: v1.5.0
>
> Attachments: FLUME-2156.patch
>
>
> When a soft restart (reconfiguration) happens, we should first unregister,
> then re-register the JMX MBean to avoid spurious error messages in the logs,
> and even breaking the metrics in some cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
