Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Peter Sabaini a écrit :
> On Tuesday 06 January 2009 10:33:33 GAUTIER Hervé wrote:
>
>> Unfortunately, I know well these states, but my question is in fact:
>> In case of split brain (and at any time), does DRBD know which member
>> still is or was primary ?
>> Or each peer does not keep any information concerning the other ? And it
>> will be to the clustering software to keep this information ?
>>
>
> Hm, you probably can parse historical state data out of the kernel logfile;
> otherwise I don't know if DRBD keeps past state data.
>
> The other question is -- what are you going to do with this information? Have
> you looked at configuring the split brain recovery policy?
Well, it is to implement a cluster manager. It will be easier if DRBD
could give me this information.
> Maybe it already
> does what you want. See http://www.drbd.org/users-guide-emb/s-configure-
> split-brain-behavior.html#s-automatic-split-brain-recovery-configuration
>
Not exactly.
In fact, it is to refuse to start a DRBD service in case of split brain
on a member which was not the last known (before split brain) running
the service.
Maybe dpod is the solution, but I am not sure.
--
Hervé GAUTIER herve.gautier([AT])thalesgroup.com
Tel: +33 (0)1 79 612 311 Fax: +33 (0)1 79 612 400
THALES AIR SYSTEMS S.A. - Customer Service / ANS department
Parc Tertiaire SILIC - 3 Avenue Charles Lindbergh
BP 20351 - 94628 Rungis Cedex - FRANCE