[DRBD-user] Avoid blocking IO when node fails

Digimer lists at alteeve.ca
Wed Feb 12 20:47:37 CET 2014

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


On 12/02/14 11:34 AM, Roberto Munoz Gomez wrote:
> Hi,
>
> I have configured an Active/Active cluster with Dual Primary DRBD. All works fine and fast.
>
> But when a node fails, the DRBD status goes to WFConnection and all IO is blocked on the other node. In this scenario I need the survivor to continue using the DRBD partition. It would be great if when the other node comes back, the synchronization begins automatically and both become Primary automatically.
>
> I have search the doc and google, but have not found any of this. Only the ko-count option, but does not seem to make a difference.
>
> Any ideas?
>
> Thanks in advance.
>
> Regards.

You need fencing to safely proceed after a node loss. Are you using cman 
or pacemaker? If so, you can setup fencing in those (pacemaker calls it 
stonith, same thing) and then hook DRBD into it.

-- 
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without 
access to education?



More information about the drbd-user mailing list