On Sun, 26 Feb 2012, James Harper <james.harper@bendigoit.com.au> wrote:
What does drbd consider to be a split brain situation?
If both nodes have been accessed as primary without synchronising with each other. You could test this like:
I have a server which is NEVER getting such a situation. It is running with one node as primary and the other as secondary and then suddenly the split- brain handler is called for no good reason that I can determine.
1. Shut down node B. 2. Make resource primary on node A 3. Write something to the resource 4. Shut down node A 5. Start up node B 6. Make resource primary on node B 7. Write something to the resource 8. Start up node A
I believe that will require that the data store is invalidated for one node before it can connect again. That's not what I'm interested in here. I'm interested in why the primary node spontaneously reboots. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/