[
https://issues.apache.org/jira/browse/ARTEMIS-2716?focusedWorklogId=615169&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-615169
]
ASF GitHub Bot logged work on ARTEMIS-2716:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 25/Jun/21 19:39
Start Date: 25/Jun/21 19:39
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 a must before
we went ahead, and the point of the call in the first place to agree on that
solution. As such the need for the journal versioning to address that. Im very
cautious about us delivering this to main and to users without an automated and
safe solution to the data state issue as its asking for production issues, and
people shooting themselves in the foot.
Further enhancements like multi slave etc was the stuff we could implement
after.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 615169)
Time Spent: 19h 50m (was: 19h 40m)
> 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 50m
> 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)
