[
https://issues.apache.org/jira/browse/ARTEMIS-3429?focusedWorklogId=641917&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-641917
]
ASF GitHub Bot logged work on ARTEMIS-3429:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 25/Aug/21 19:07
Start Date: 25/Aug/21 19:07
Worklog Time Spent: 10m
Work Description: franz1981 commented on pull request #3694:
URL: https://github.com/apache/activemq-artemis/pull/3694#issuecomment-905799632
Good point, I would add a cli command (or expose a control) to modify the
coordinated activation sequence (on zookeeper) and allow a broker to correctly
start. This is for proper disaster cases
--
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: 641917)
Time Spent: 40m (was: 0.5h)
> Backup forget coordination-id after quorum loss
> -----------------------------------------------
>
> Key: ARTEMIS-3429
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3429
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.18.0
> Reporter: Francesco Nigro
> Assignee: Francesco Nigro
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Assuming a multi-primary set-up, if the broker acting as backup lost quorum,
> is restarted without applying the coordination-id patching on NodeManager:
> if its local activation sequence is > 0 (because of a past sync with the
> other live) the backup succeed to activate, causing a split-brain (although
> its NodeID is a random one vs the original coordination-id).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
