Are you sure that the code will ensure a graceful and speedy shutdown when the broker loses a lock but stays up? Last time I looked at this (admittedly, not in all that much detail, and I've meant to make time for that ever since and haven't done so), I came away with the impression that the locking logic worked fine for brokers that had never previously become the master, but not necessarily for brokers that were already the master and lost it. On Feb 29, 2016 8:35 PM, "artnaseef" <a...@artnaseef.com> wrote:
> Something sounds very wrong there. The NFS lock file should prevent more > than one broker writing to the store at a time. > > Is all of /var/log/activemq/activemq-data/ shared across all of the > brokers? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/question-for-users-of-NFS-master-slave-setups-tp4708204p4708618.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
