You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@helix.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2014/07/16 22:35:04 UTC
[jira] [Commented] (HELIX-471) ResourceMonitor never unregistered
even if the resource is dropped
[ https://issues.apache.org/jira/browse/HELIX-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064042#comment-14064042 ]
Hudson commented on HELIX-471:
------------------------------
UNSTABLE: Integrated in helix #1264 (See [https://builds.apache.org/job/helix/1264/])
[HELIX-471] Unregister ResourceMonitor on drop (kanak: rev 8f90279b062408e08c17aa5473d41506f3e39ba3)
* helix-core/src/test/java/org/apache/helix/monitoring/mbeans/TestDropResourceMetricsReset.java
* helix-core/src/main/java/org/apache/helix/monitoring/mbeans/ClusterStatusMonitor.java
* helix-core/src/main/java/org/apache/helix/controller/stages/ExternalViewComputeStage.java
> ResourceMonitor never unregistered even if the resource is dropped
> ------------------------------------------------------------------
>
> Key: HELIX-471
> URL: https://issues.apache.org/jira/browse/HELIX-471
> Project: Apache Helix
> Issue Type: Bug
> Reporter: Kanak Biscuitwala
> Assignee: Kanak Biscuitwala
>
> When we drop a resource, we should remove the registered bean containing metrics specific to that resource. Right now, it just stays around without being updated.
--
This message was sent by Atlassian JIRA
(v6.2#6252)