[DRBD-user] out-of-sync based on AL

Lars Ellenberg Lars.Ellenberg at linbit.com
Thu Feb 15 17:45:54 CET 2007

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


/ 2007-02-15 16:29:48 +0000
\ Cristian Zamfir:
> 
> Hi,
> 
> I just figured out that this is happening only when I am detaching two primaries.
> Switching from primary to secondary before detach does not produce any resync.
> 
> From the man, "In case a primary node leaves the cluster unexpectedly  the  areas  covered  by
> the active set must be resynced upon rejoin of the failed node"
> 
> But in this case I am manually detaching so it is not an unexpected leave from a primary node.
> Is this a bug or is it the intended behaviour?

actually, if you detach a node while it is Primary, you should later get
a FULL SYNC, because we should assume that you did so because the
backing storage is to be replaced. so if we fix something in that area,
it be likely that.

just don't detach on a node while it is Primary.

-- 
: Lars Ellenberg                            Tel +43-1-8178292-0  :
: LINBIT Information Technologies GmbH      Fax +43-1-8178292-82 :
: Vivenotgasse 48, A-1120 Vienna/Europe    http://www.linbit.com :
__
please use the "List-Reply" function of your email client.



More information about the drbd-user mailing list