[ 
https://issues.apache.org/jira/browse/HELIX-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14063813#comment-14063813
 ] 

Hudson commented on HELIX-132:
------------------------------

SUCCESS: Integrated in helix #1262 (See 
[https://builds.apache.org/job/helix/1262/])
[HELIX-132] current-state and external-view are not cleaned up when a resource 
has been removed, rb=21666 (zzhang: rev 
b470ababa8727fc5534bc8dc00b3f4a3cd9076e8)
* 
helix-core/src/main/java/org/apache/helix/controller/stages/ResourceComputationStage.java
* helix-core/src/main/java/org/apache/helix/manager/zk/ZKHelixDataAccessor.java
* helix-core/src/test/java/org/apache/helix/integration/TestDrop.java
* 
helix-core/src/main/java/org/apache/helix/controller/stages/ExternalViewComputeStage.java
* helix-core/src/main/java/org/apache/helix/GroupCommit.java


> current-state and external-view are not cleaned up when a resource has been 
> removed
> -----------------------------------------------------------------------------------
>
>                 Key: HELIX-132
>                 URL: https://issues.apache.org/jira/browse/HELIX-132
>             Project: Apache Helix
>          Issue Type: Bug
>            Reporter: Zhen Zhang
>            Assignee: Zhen Zhang
>              Labels: newbie
>
> we leave an empty current-state and external-view when a resource has been 
> dropped. for systems that frequently add/drop resources, this leave many 
> empty znodes under current-state and external-view. we need:
> 1) fix this in helix
> 2) have a tool that auto clean current-state and external-view for dropped 
> resources



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to