[
https://issues.apache.org/jira/browse/ARTEMIS-2716?focusedWorklogId=605822&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-605822
]
ASF GitHub Bot logged work on ARTEMIS-2716:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 03/Jun/21 10:26
Start Date: 03/Jun/21 10:26
Worklog Time Spent: 10m
Work Description: franz1981 edited a comment on pull request #3555:
URL: https://github.com/apache/activemq-artemis/pull/3555#issuecomment-853764285
I've decided 2 important things re this PR:
- going to drop Atomix support -community is not reactive and the solution
itself doesn't seem solid as expected -
- there are some loop in the primary state diagram that can be dangerous:
*on primary start*: we loop forever searching some broker with the same Node
ID to pair with (to failback) or we try acquire the live lock -> both should be
attempted just once
*during failback*: if the failback process is going to fail, the primary is
restarting as primary, getting into the loop mentioned above -> it should just
stop
@jbertram @gtully Any opinons?
--
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: 605822)
Time Spent: 7.5h (was: 7h 20m)
> 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: 7.5h
> 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)
