You are viewing a plain text version of this content. The canonical link for it is here.
Posted to gitbox@activemq.apache.org by GitBox <gi...@apache.org> on 2021/09/01 16:50:11 UTC

[GitHub] [activemq-artemis] gtully edited a comment on pull request #3694: ARTEMIS-3429-3430-3446 Fixes for pluggable quorum vote activation sequence

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: gitbox-unsubscribe@activemq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org