[
https://issues.apache.org/jira/browse/ARTEMIS-3429?focusedWorklogId=645378&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-645378
]
ASF GitHub Bot logged work on ARTEMIS-3429:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 01/Sep/21 16:50
Start Date: 01/Sep/21 16:50
Worklog Time Spent: 10m
Work Description: gtully edited a comment on pull request #3694:
URL: https://github.com/apache/activemq-artemis/pull/3694#issuecomment-910466759
for the cli, it needs to be very scenario and play book driven. For example:
Scenario:
1. zk has burned, restarted and is empty!
2. broker fails to start with activation sequence X and coordinated
sequence 0 (presumably)
Play book:
in this case, we need check each brokers activation sequence and push the
largest to zk.
nodeA> artemis activation list
nodeA> X
nodeB> artemis activation list
nodeB> Y
nodeA|B> artemis activation push
I guess list could be show.
if the return code from artemis activation list is an int (of the local
activation sequence), this can be scripted nicely.
maybe: artemis activation list --remote is the value from zk.
just some thoughts :-)
another scenario:
1. live has burned
2. backup has archived stale data that is now all we have.
play book:
move the backup archive to current data
push the current (stale) activation sequence: nodeX> artemis activation
push --force (b/c it will be stale)
--
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: 645378)
Time Spent: 2h 10m (was: 2h)
> 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: 2h 10m
> 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)
