[DRBD-user] Guarantee write to both nodes

Lars Ellenberg lars.ellenberg at linbit.com
Fri Mar 19 17:02:20 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 Fri, Mar 19, 2010 at 05:24:48PM +0200, 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.

In short, the feature you requests is somewhere on the far end of our
todo list. But feel free to reprioritize...

: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
please don't Cc me, but send to list   --   I'm subscribed

More information about the drbd-user mailing list