Thank you for your responses, Justin. Also thank you for noting the journal backup feature. That's great news. :)
Meanwhile, I've developed a simple scripted solution that works for statically configured clusters such as mine. It simply extracts the broker configuration and state (the last time it went live) and publishes it on a certain port. Then each broker instance has its own preloader which decides whether its safe to start the broker or not just by looking at the state of each of the other brokers within the cluster. Once it learns that it's safe to start the instance it just returns RC 0, thus it can be used as ExecStartPre in *.service files. In case of RC != 0 systemd waits for a while and then tries again. It's not stable yet but I'll happily publish the draft if anyone happens to be interested. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
