[
https://issues.apache.org/jira/browse/ARTEMIS-2716?focusedWorklogId=606029&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-606029
]
ASF GitHub Bot logged work on ARTEMIS-2716:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 03/Jun/21 16:05
Start Date: 03/Jun/21 16:05
Worklog Time Spent: 10m
Work Description: michaelpearce-gain edited a comment on pull request
#3555:
URL: https://github.com/apache/activemq-artemis/pull/3555#issuecomment-853978150
If the primary was restarted whilst isolated, it shouldnt be able to get the
lock from ZK....... im clearly missing something. I would expect the primary to
start, just simply it cannot join the cluster and it just keeps trying,
ommitting errors and warnings in logs , and if we have a health endpoint (for
k8s) maybe could report not ready status.
Just like with the network health checker today, the jvm process is up, but
the server inside isnt started, and simply it keeps re-trying.
You could do similar, if you cant talk to ZK at all (ignore lock) you have
jvm up, but server inside is in stopped state and just keep retrying.
--
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 606029)
Time Spent: 12h 40m (was: 12.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: 12h 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)
