[
https://issues.apache.org/jira/browse/HELIX-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16524288#comment-16524288
]
ASF GitHub Bot commented on HELIX-705:
--------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/helix/pull/204
> 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)
