[
https://issues.apache.org/jira/browse/HELIX-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16524291#comment-16524291
]
Hudson commented on HELIX-705:
------------------------------
FAILURE: Integrated in Jenkins build helix #1471 (See
[https://builds.apache.org/job/helix/1471/])
[HELIX-705]: Participant duplicated state transition handling rework (hrzhang:
rev 8dc19afb9b70d262da0eb2081840d65f2a031122)
* (edit)
helix-core/src/main/java/org/apache/helix/messaging/handling/HelixStateTransitionHandler.java
* (edit)
helix-core/src/test/java/org/apache/helix/messaging/handling/TestHelixTaskExecutor.java
* (edit)
helix-core/src/main/java/org/apache/helix/messaging/handling/HelixTaskExecutor.java
* (edit)
helix-core/src/main/java/org/apache/helix/messaging/handling/HelixTask.java
> Participant duplicated state transition handling rework
> -------------------------------------------------------
>
> Key: HELIX-705
> URL: https://issues.apache.org/jira/browse/HELIX-705
> Project: Apache Helix
> Issue Type: Task
> Reporter: Hao Zhang
> Priority: Major
>
> Helix should have some re-work on participant side message handling:
> - Duplicated message in same batch: discard the later one
> - Duplicated message in different batches, the later one should be discarded
> if the first one is in progress
> - During state transition, we should not rely on current state delta to get
> partition's current state, but should lock on state model def (thread safety)
> - Duplicated state transition (toState == currentState) should not result in
> error, which is confusion, but should report success
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
