Details
-
Task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
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
Attachments
Issue Links
- links to
