As far as a broker properly cleaning up when active and losing the lock -- first off, that's a very rare scenario. With that said, there's no way to guarantee a completely clean hand-off at that point. The cause of such a scenario will be a drop in network communication between that broker and the NFS server.
When that happens, there may be writes buffered by that broker's O/S that will be sent to the server once communication is restored. Therefore, an active broker losing its lock is a very bad scenario, and the best action to take in that case is to look at the underlying hardware, network components and settings, and the O/S in order to stabilize the networking. In extreme cases of H/A, the server can be built-out with full redundancy in the network (i.e. two network cards connected to two different switches, etc). -- View this message in context: http://activemq.2283324.n4.nabble.com/question-for-users-of-NFS-master-slave-setups-tp4708204p4708645.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
