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

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

                Author: ASF GitHub Bot
            Created on: 28/Jun/21 11:12
            Start Date: 28/Jun/21 11:12
    Worklog Time Spent: 10m 
      Work Description: michaelandrepearce commented on pull request #3555:
URL: https://github.com/apache/activemq-artemis/pull/3555#issuecomment-869595312


   Indeed, but i think we need both parts before we goto main, id be concerned 
about this going into main before that as then we could accidentally release 
just one part and people getting themselves into an issue in prod, without both 
parts being done, and protecting people from themselves.


-- 
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.

To unsubscribe, e-mail: gitbox-unsubscr...@activemq.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


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

    Worklog Id:     (was: 615554)
    Time Spent: 21h  (was: 20h 50m)

> 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: 21h
>  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