From: Lars Marowsky-Bree <lmb@suse.de>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] Summary (2nd try)
Date: Wed, 25 Aug 2004 15:09:34 +0200 [thread overview]
Message-ID: <20040825130934.GZ3125@marowsky-bree.de> (raw)
In-Reply-To: <200408251501.59314.philipp.reisner@linbit.com>
On 2004-08-25T15:01:59,
Philipp Reisner <philipp.reisner@linbit.com> said:
> Hi,
>
> After I realized that we no longer make any node primary automatically :)
> Here the suggestion of the new configure option:
>
> after-primary-primary =
This is in case where after the reconnect there is no primary (s/s),
right?
> disconnect No automatic resynchronisation gets performed. One
> node should drop its net-conf (preferable the
> node that would become sync-target)
> I think this should be default.
> ass-older Auto sync source is the oder primary (current default i.t.s.)
> ass-younger Auto sync source is the younger primary
> ass-furthest Auto sync source is the node that did more modifications
> ass-NODENAME Auto sync source is the named node
>
> Falls es schon einen pirmary gibt (also dieses:
>
[snip]
> ) Dann:
>
> disconnect (current behaviour in the situation.)
> ass-* Auto sync, but the current primary gets sync-source.
>
> What do you think ?
Sounds good, one scenario is missing.
P-P scenario:
disconnect (same same)
ass-* the node which would be SyncTarget needs to crash
itself to 'clear' the higher levels, and then would
(after the reboot) go through the first scenario.
This may be useful for unattended embedded scenarios, but as it is
pretty severe recovery for a grave error, may even value an additional
flag.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering \\\ ///
SUSE Labs, Research and Development \honk/
SUSE LINUX AG - A Novell company \\//
prev parent reply other threads:[~2004-08-25 13:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 13:01 [Drbd-dev] Summary (2nd try) Philipp Reisner
2004-08-25 13:09 ` Lars Marowsky-Bree [this message]
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=20040825130934.GZ3125@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