Also, you could consider using a RDBMS as your backing store. It's had less
tuning than KahaDB, and it's not particularly well supported on this
mailing list because I've never used it and I'm not sure if any of the
other active responders have either, but it's more stable than LevelDB and
it doesn
ActiveMQ allows pluggable storage lockers (
http://activemq.apache.org/pluggable-storage-lockers.html) which allow you
to use a different technology for master election than you use for message
storage. So the inability of a shared filesystem technology to provide
distributed file locks isn't a dea
I would suggest checking out something like GlusterFS which created distributed
replicated data. We have used it for high performant applications without
problem. I am not sure how the slave knows how to not start - so this may not
work for you if it is based on file locking.
Thanks
Steve
> O
This doesn't directly answer your question, but...
Aside from using the 5.x broker you can use the ActiveMQ Artemis broker [1].
It supports shared-nothing replication for live/backup. See more in the
documentation [2].
Justin
[1] http://activemq.apache.org/artemis/
[2] http://activemq.apach
