-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
Quorum Vote
-
Documentation (Ref Guide, User Guide, etc.), Release Notes, Migration, Compatibility/Configuration, User Experience
-
To Do
-
High
-
0% To Do, 0% In Progress, 100% Done
This epic aim to implement a new Quorum Vote mechanism for AMQ with the objectives:
- to make it pluggable
- to cleanly separate the election phase and the cluster member states
- to simplify most common setups in both amount of configuration and requirements
A proposal of steps to be followed to get this is:
- abstract away the current quorum vote: it requires extra-care because the
logic is mixed together with the replication/clustering behaviour - refactor it in order to separate election phase and cluster member states
- implement a RI version using a specific consensus provider (eg zookeeper, jgroup-raft)
About the last point, we need extra care to correctly handle the community requirements to get it accepted.
Post-actions to help people adopt it, but need to be thought upfront:
- a clean upgrade path for current HA replication users
- deprecate or integrate the current HA replication into the new version
- relates to
-
ENTMQBR-2291 [AMQ7, replicated master slave, restart] potential for message loss if restarted in wrong order
-
- Closed
-
-
-
- Closed
-
There are no Sub-Tasks for this issue.
