[Drbd-dev] Re: drbd Frage zu secondary vs primary;
drbddisk status problem
philipp.reisner at linbit.com
Wed Aug 25 13:30:17 CEST 2004
On Wednesday 25 August 2004 12:28, Lars Marowsky-Bree wrote:
> On 2004-08-25T11:42:18,
> Philipp Reisner <philipp.reisner at linbit.com> said:
> > So, the current policy is:
> > * The primary node refuses to connect to a peer with higher generation
> > counts. This keeps the data intact. This is very related to the other
> > after-split-brain-policy I want to make expclicit.
> Makes sense.
> > * Remeber the options so far: (for primary-after-split-brain)
> > - The node that was primary before split brain (current behaviour)
> > - The node that became primary during split brain
> > - The node that modified more of it's data during the split-brain
> > situation [ Do not think about implementation yet, just about
> > the policy ]
> > - None, wait for operator's decission. [suggested by LMB]
> > - Node that is currently primary [see example above by LGE]
> Minor clarification: I think the question is not about "Who becomes
> primary", as the Sync* is decoupled from that status, but which side
> drbd deems to have the good data and thus the SyncMaster.
Right. It is really a shame that I have not yet fully realized
that drbd-7 is the current stable release :)
> Looking at it from this angle, we have two dimensions:
> - Node state after the split-brain heals. Each side can either be
> primary or secondary.
> - The data state on each side.
I will post a new version of the "Summary" mail...
: Dipl-Ing Philipp Reisner Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
: Schönbrunnerstr 244, 1120 Vienna, Austria http://www.linbit.com :
More information about the drbd-dev