You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@helix.apache.org by "Hao Zhang (JIRA)" <ji...@apache.org> on 2018/06/25 22:52:00 UTC

[jira] [Created] (HELIX-705) Participant duplicated state transition handling rework

Hao Zhang created HELIX-705:
-------------------------------

             Summary: 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


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)