You are viewing a plain text version of this content. The canonical link for it is here.
Posted to gitbox@activemq.apache.org by GitBox <gi...@apache.org> on 2021/06/03 10:55:36 UTC
[GitHub] [activemq-artemis] gtully commented on pull request #3555: ARTEMIS-2716 Implements pluggable Quorum Vote
gtully commented 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 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:
users@infra.apache.org