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

ASF GitHub Bot logged work on ARTEMIS-2716:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 03/Jun/21 15:02
            Start Date: 03/Jun/21 15:02
    Worklog Time Spent: 10m 
      Work Description: michaelpearce-gain edited a comment on pull request 
#3555:
URL: https://github.com/apache/activemq-artemis/pull/3555#issuecomment-853937157


   So the instance shouldn't even be trying to even get the lock until it is 
back "back-in-sync", it should only be trying to get the lock in case it 
"could" take over, just as today, a slave cannot become active until it was 
data-in-sync, this is seperate to leader election, it simply isnt eligible for 
being a leader until it is. 


-- 
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:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 605980)
    Time Spent: 11h 40m  (was: 11.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: 11h 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)

Reply via email to