[
https://issues.apache.org/jira/browse/ARTEMIS-3429?focusedWorklogId=646849&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-646849
]
ASF GitHub Bot logged work on ARTEMIS-3429:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 06/Sep/21 10:43
Start Date: 06/Sep/21 10:43
Worklog Time Spent: 10m
Work Description: gtully commented on a change in pull request #3694:
URL: https://github.com/apache/activemq-artemis/pull/3694#discussion_r702801235
##########
File path: docs/user-manual/en/activation-tools.md
##########
@@ -0,0 +1,46 @@
+# Activation Sequence Tools
+
+You can use the Artemis CLI to execute activation sequence
maintenance/recovery tools
+for [Pluggable Quorum Replication](ha.md).
+
+The 2 main commands are `activation list` and `activation set`, that can be
used together to recover some disaster
+happened to local/coordinated activation sequences.
+
+Here a disaster scenario built around the RI (using [Apache
Zookeeper](https://zookeeper.apache.org/)
+and [Apache curator](https://curator.apache.org/)) to demonstrate the usage of
such commands.
+
+## Troubleshooting Case: Zookeeper Cluster disaster
+
+A proper Zookeeper cluster should use at least 3 nodes, but what happen if all
these nodes crash loosing any activation
Review comment:
or 'will happen'
--
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: 646849)
Time Spent: 3h 20m (was: 3h 10m)
> 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: 3h 20m
> 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)
