[
https://issues.apache.org/jira/browse/ARTEMIS-2716?focusedWorklogId=615546&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-615546
]
ASF GitHub Bot logged work on ARTEMIS-2716:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 28/Jun/21 10:56
Start Date: 28/Jun/21 10:56
Worklog Time Spent: 10m
Work Description: michaelandrepearce commented on pull request #3555:
URL: https://github.com/apache/activemq-artemis/pull/3555#issuecomment-869585010
And here lies the biggest issue, the human. This is what and why this was
something to be solved, because too often than not, the human cannot make the
right decision, starts accidentally the wrong node, so forth and so on.
And thus why we had the call to find the solution. Now the agreed solution
from call was the journal solution proposed by youself, but we do need
something. If we dont think journal solution now work, then we should probably
have a follow up call. but i suspect thats not the case here.
--
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: 615546)
Time Spent: 20h 40m (was: 20.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: 20h 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)
