helix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hao Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HELIX-705) Participant duplicated state transition handling rework
Date Mon, 25 Jun 2018 22:52:00 GMT
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

View raw message