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

Hudson commented on HELIX-682:
------------------------------

FAILURE: Integrated in Jenkins build helix #1451 (See 
[https://builds.apache.org/job/helix/1451/])
[HELIX-682] delete duplicated message and log error in HelixTaskExecutor 
(zhan849: rev 5f9fadc72bc1916f008792707db848ee51bbd997)
* (edit) 
helix-core/src/test/java/org/apache/helix/messaging/handling/TestHelixTaskExecutor.java
* (edit) helix-core/src/test/java/org/apache/helix/MockAccessor.java
* (edit) 
helix-core/src/main/java/org/apache/helix/messaging/handling/HelixTaskExecutor.java


> Stale message should not prevent controller from rebalancing resource
> ---------------------------------------------------------------------
>
>                 Key: HELIX-682
>                 URL: https://issues.apache.org/jira/browse/HELIX-682
>             Project: Apache Helix
>          Issue Type: Bug
>            Reporter: Hao Zhang
>            Priority: Major
>
> Currently during MessageGenerationPhase, we skip re-balancing when there is 
> pending message. Though we assume that participant will delete messages when 
> they finish the task, there will be cases that when ZK is not stable and 
> participant fail to do so, which will leave message un-deleted and thus block 
> rebalance.
> Ideally on controller side, we should try to delete message as well: if 
> partition's current state is same as message's toState, or there is totally 
> invalid message remaining, controller should try to delete message to unblock 
> rebalancing



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to