On 11/01/11 08:13, Aleksandar Ivanisevic wrote: > "Frank" <[email protected]> writes: > > >> We use pacemaker to start/stop VEs and to be sure they only run on one >> node. Anyway crashes happen periodicly. We have about 40 VEs >> distributed >> > Pacemaker is nice, but if it fails (think split brain), there is > really nothing to prevent data loss. > > How do you handle split brain on a shared volume when you have half of > VEs running on each side? >
That's unlikely with our topology (one half of the split is likely to have no connectivity, and therefore the changes there can be discarded), and we would do manual split brain recovery if necessary (haven't had to yet). We don't currently use drbd in multi-master mode, instead we have a number of drbds per node pair, and all the VEs associated with a given drbd must run on the same node at the same time. Another way to solve the problem would be to use similar methods to OCFS2 etc. (AFAIK) i.e. corosync instead of heartbeat (and use more than two nodes in your corosync totem ring) and set your quorum to prevent split-brain occurring at all. Cheers, Tim. -- South East Open Source Solutions Limited Registered in England and Wales with company number 06134732. Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ VAT number: 900 6633 53 http://seoss.co.uk/ +44-(0)1273-808309 _______________________________________________ Users mailing list [email protected] https://openvz.org/mailman/listinfo/users
