[
https://issues.apache.org/jira/browse/ARTEMIS-2716?focusedWorklogId=615131&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-615131
]
ASF GitHub Bot logged work on ARTEMIS-2716:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 25/Jun/21 17:56
Start Date: 25/Jun/21 17:56
Worklog Time Spent: 10m
Work Description: franz1981 edited a comment on pull request #3555:
URL: https://github.com/apache/activemq-artemis/pull/3555#issuecomment-868733034
> All you are doing by it not is making it manual intervention which you
operationally want to not do. And what is an operator to do. Restart it.... so
your not getting any win.
Are you talking about primary start loop, now missing, or about the
automatic activation/deactivation of primary because of unavailable quorum
service?
The latter has been discussed during the community call and the reason why
it hasn't been implemented was because of missing journal versioning: without
journal versioning there is no point to quickly restart, because it just
increase the chance of journal misalignments.
We can safely introduce it later, when the version allow to check if the
broker is not just live, but with the most up to date journal.
Right now, it's not suggested to quickly restart a primary without checking
who was the last broker alive with the same ID: the same with classic
replication. More details on the ref JIRA about journal versioning linked on
the original JIRA of this pr.
I'm not against self-healing but I believe this should be introduced with
the right feature to make it reliable, or is just self-misaligning.
Or maybe I have misunderstood (Friday brain :( ) and you were talking about
https://github.com/apache/activemq-artemis/pull/3555#issuecomment-867383785?
If yes, sorry for the super long comment above, I promise I will answer it
on Monday :)
--
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: 615131)
Time Spent: 18h 10m (was: 18h)
> 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: 18h 10m
> 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)
