From: Lars Marowsky-Bree <lmb@suse.de>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] Re: drbd Frage zu secondary vs primary; drbddisk status problem
Date: Mon, 23 Aug 2004 23:56:56 +0200 [thread overview]
Message-ID: <20040823215656.GC17118@marowsky-bree.de> (raw)
In-Reply-To: </+7SE+vRTb9mi3m45Lh2qDY=lge@web.de>
On 2004-08-20T15:32:15,
Lars Ellenberg <Lars.Ellenberg@linbit.com> said:
> N1 N2
> P --- S Everything ok.
> P - - S N1 is failing, but for the moment being just can no
> longer answer the network; but it is still able to update
> drbds generation counts
> ? - S Now N1 may be dead, or maybe not
> X - S A sane Cluster-mgr makes N2 primary, but stonith N1 first ...
As you pointed out, the sane cluster manager (or admin) ought to be
setting a Kain flag when it knows for sure it has slain it's brother...
Now, that would even help catch the case where the crm had a malfunction
and made both sides primary, in which case it really really shouldn't
automatically connect, but will require higher level help (to make one
side secondary first).
> X - P N1 now is really dead.
> S --- P N1 comes back
> S - : P oops, N1 has "better" generation counts than N2
> N2 shall become sync target, but since it is
> currently Primary, it will refuse this.
> It goes standalone.
>
> Now, I think in that case, N1 needs special handling of the situation,
> too, which it currently has not.
> Yet an other deficiency:
> we still do not handle the gencounts correctly in this situation:
>
> S --- S
> P --- S drbdsetup primary --human
> now, N1 increments its human cnt, N2 only its connection count after
> failure of N1, N2 will take over, maybe be primary for a whole week.
> then N1 comes back, has the higher human count, and will
> either [see above] (if N2 still is Primary)
> or wipe out a week worth of changes (if N2 was demoted to Secondary
> meanwhile).
>
> Oops :-(
Ouchie. Probably should send that across the wire...
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering \ This space /
SUSE Labs, Research and Development | intentionally |
SUSE LINUX AG - A Novell company \ left blank /
next prev parent reply other threads:[~2004-08-23 21:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040819110202.GO9601@marowsky-bree.de>
[not found] ` <20040819113205.GP9601@marowsky-bree.de>
[not found] ` <R+ahoCHARbsLOMKIahWH0/Q=lge@web.de>
2004-08-20 12:52 ` [Drbd-dev] Re: drbd Frage zu secondary vs primary; drbddisk status problem Philipp Reisner
2004-08-20 13:32 ` Lars Ellenberg
2004-08-23 14:28 ` [Drbd-dev] gen_counts and primary --human Lars Ellenberg
2004-08-23 21:57 ` Lars Marowsky-Bree
2004-08-25 9:42 ` Philipp Reisner
2004-08-23 21:56 ` Lars Marowsky-Bree [this message]
2004-08-25 9:42 ` [Drbd-dev] Re: drbd Frage zu secondary vs primary; drbddisk status problem Philipp Reisner
2004-08-25 10:28 ` Lars Marowsky-Bree
2004-08-25 11:30 ` Philipp Reisner
2004-08-25 13:38 ` Lars Ellenberg
2004-09-04 9:48 ` [Drbd-dev] Another drbd race Lars Marowsky-Bree
2004-09-04 10:00 ` Lars Ellenberg
2004-09-04 10:18 ` Lars Marowsky-Bree
2004-09-04 10:43 ` Lars Ellenberg
2004-09-04 10:51 ` Lars Marowsky-Bree
2004-09-07 9:39 ` Philipp Reisner
2004-09-07 10:13 ` Lars Ellenberg
2004-09-07 11:32 ` Philipp Reisner
2004-09-07 12:05 ` Lars Ellenberg
2004-09-07 12:12 ` Lars Marowsky-Bree
2004-09-07 12:06 ` Lars Marowsky-Bree
2004-09-07 12:19 ` Philipp Reisner
2004-09-07 12:28 ` Lars Marowsky-Bree
2004-09-07 12:47 ` Philipp Reisner
2004-09-08 11:20 ` Lars Marowsky-Bree
2004-09-08 11:31 ` Lars Ellenberg
2004-09-08 15:11 ` Lars Marowsky-Bree
2004-09-08 15:22 ` Lars Ellenberg
2004-09-08 11:33 ` Philipp Reisner
2004-09-07 15:55 ` Lars Ellenberg
2004-08-20 14:10 ` [Drbd-dev] Re: drbd Frage zu secondary vs primary; drbddisk status problem Helmut Wollmersdorfer
2004-08-23 22:01 ` Lars Marowsky-Bree
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040823215656.GC17118@marowsky-bree.de \
--to=lmb@suse.de \
--cc=drbd-dev@lists.linbit.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox