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

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

                Author: ASF GitHub Bot
            Created on: 25/Jun/21 19:34
            Start Date: 25/Jun/21 19:34
    Worklog Time Spent: 10m 
      Work Description: michaelandrepearce edited a comment on pull request 
#3555:
URL: https://github.com/apache/activemq-artemis/pull/3555#issuecomment-868788409


   So i thought we had a data state issue and thus a solution was must before 
we went ahead, and the point of the call in the first place. As such the need 
for the journal versioning to address that. Im very cautious about us 
delivering this to main and to users without a solution to that issue as its 
asking for production issues. 


-- 
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: 615165)
    Time Spent: 19h 20m  (was: 19h 10m)

> 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: 19h 20m
>  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