[DRBD-user] Guarantee write to both nodes

Digimer linux at alteeve.com
Fri Mar 19 17:38:11 CET 2010

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

On 10-03-19 11:24 AM, Yuri Ushakov wrote:
> I need synchronous replication over network, but with one strict rule -
> if DRBD says something is written, it should already be written to both
> nodes. When secondary is down, and DRBD is still writing to the primary
> - that is not really synchronous replication. That behaviour makes it
> asynchronous, because actual write to the secondary node is delayed.
> In general, I want to ensure that when database transaction is commited,
> the data rests on both nodes. If secondary is unavailable, transaction
> should be rolled back.
> Thanks,
> Yuri.

Hmm, it seems like it's a bit outside of the original goal of DRBD, but 
it might be doable via the 'on-io-error' or 'fencing' options. Take a 
look at this: http://www.drbd.org/users-guide/re-drbdconf.html

E-Mail:         linux at alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin:  http://nodeassassin.org

More information about the drbd-user mailing list