Quote:
Originally Posted by sems  Heartbeat does in R1 mode does not check the status of each resource, whether they are up or down. So, you'll need to implement something, like MON package to monitor zimbra status and if needed stop heartbeat accordingly.
Hizar,
In your setup, I haven't seen anything related to split-brain on DRBD. That has been my major issue (I have been running an active/passive cluster since March, but it always comes back as a problem). How do you deal with it on yours? I have been searching on the net for possible ways to prevent split-brain to happen in the first place. I found some articles suggesting to increase heartbeat's drbddisk script's retry from 6 to 20 and increasing timeout values (see Otherworldly Gate: STONITH with DRBD and Heartbeat), I haven't tried it yet but I am open to suggestions. |
Yes this is an issue with my setup. I've never really understood how this whole Stonith thing is supposed to work and when I've tried it, it hasnt quite given me the results I was expecting. Other than a Stonith device, it seems hard to get stonith to work properly. (If the network between the two hosts is down, then how is one host supposed to kill the other?)
The other thing I tried that got me mixed results is setting up 'Shoot myself in the Head' which as it sounds is when the other host is unreachable, kill yourself.
This has the effect that both servers recover after a minimal downtime, but its hardly High Availability.
The other problem I had was sometimes it refused to work because something was holding the DRBD partition open and would not die.