[jira] [Comment Edited] (ARTEMIS-2716) Implements pluggable Quorum Vote

["Francesco Nigro (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17331909#comment-17331909 ] 

Francesco Nigro edited comment on ARTEMIS-2716 at 4/26/21, 8:57 AM:
--------------------------------------------------------------------

These are the drafts of the detailed state diagram of both activation roles (primary/backup) that really are 1:1(ish) with the existing master-slave.
 Primary:

!primary.png|width=797,height=628!

And backup (that includes the failback case too):

!backup.png|width=863,height=1145!

These will change over time, but gives a broad idea of how the process have changed if compared with the existing replication mechanism.
 It's similar but won't let some of the states to be undefined or un-handled.


was (Author: nigrofranz):
These are the drafts of the detailed state diagram of both activation roles (primary/backup) that really are 1:1(ish) with the existing master-slave.
Primary:

 !primary.png! 

And backup (that includes the failback case too):

 !backup.png! 

These will change over time, but gives a broad idea of how the process have changed if compared with the existing replication mechanism.
It's similar but won't let some of the states to be undefined or un-handled.


> 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: 0.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)