[
https://issues.apache.org/jira/browse/ARTEMIS-2716?focusedWorklogId=606757&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-606757
]
ASF GitHub Bot logged work on ARTEMIS-2716:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 04/Jun/21 08:21
Start Date: 04/Jun/21 08:21
Worklog Time Spent: 10m
Work Description: gtully edited a comment on pull request #3555:
URL: https://github.com/apache/activemq-artemis/pull/3555#issuecomment-853780478
I think you are right.
I would go further, and drop the fail-back feature in favour of a (jmx)
shutdown with delayed (after lock release sleep(epoch)) jvm exit.
Have a broker role be determined by the shared lock, the first to acquire
becomes primary, the others potential backups.
The existing roles flow from the possibility of unilateral decisions, two
primary brokers could be two live brokers in error. However with a reliable
distributed lock and no unilateral decisions (exit once state is unknown)
multiple competing brokers are fine.
This is a simpler model, easier to reason about and totally deterministic.
Availability is tied to the quorum. To have more HA in the event of a lock
service outage (ie quorum nodes fail), introduce another cluster of nodes.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 606757)
Time Spent: 13h 40m (was: 13.5h)
> 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: 13h 40m
> 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)
