I'm not aware of any plans to implement what you suggest here. It seems to me that if you want to mitigate the risk of split brain and you have access to shared storage then you should just use a shared store configuration instead of replication. The main benefit of replication that you don't need shared storage.
I think it's more likely that raft [1] integration would be implemented. Justin [1] https://raft.github.io/ On Mon, Oct 14, 2019 at 3:36 PM blue_nekton <jesuruban...@gmail.com> wrote: > Hi, > > For small environment to use High availability, it is often difficult to > setup 3-pair cluster to avoid split-brain. > It would be great if artemis master and slave use data replication and use > shared store only for lock and providing HA . So anytime, master/slave > verifies and gets lock before take control of being master again. it will > be > like hybrid of replication and shared store. Do we have any feature or > planning for this kind of feature? > > if that is not possible, if Artemis can allow the custom locking method to > get lock (instead of just network pinger) like a custom rest call, it will > be easy for work-around for split-brain. > > Thanks > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >
