[ https://issues.apache.org/jira/browse/ARTEMIS-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17363673#comment-17363673 ]
Francesco Nigro commented on ARTEMIS-2716: ------------------------------------------ I've decided that a failing fail-back is going to fail-fast (because it's supposed to be an admin operation), but a proper fail during a proper failover will keep the primary broker (acting as backup) alive and retry to sync with another (or the same) live. This should be cover the need to have a symmetric behaviour between a natural born-backup and a primary acting as a backup (with a backup acting as live that has configured {{allow-failback == false}}). > Implements pluggable Quorum Vote > -------------------------------- > > Key: ARTEMIS-2716 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2716 > Project: ActiveMQ Artemis > Issue Type: New Feature > Reporter: Francesco Nigro > Assignee: Francesco Nigro > Priority: Major > Attachments: backup.png, primary.png > > Time Spent: 16h > Remaining Estimate: 0h > > This task aim to ideliver a new Quorum Vote mechanism for artemis 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 (eg "witness" nodes could be implemented to support single > master-slave pairs) > 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 -- This message was sent by Atlassian Jira (v8.3.4#803005)