From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: [Drbd-dev] Summary (3rd try)
Date: Wed, 25 Aug 2004 17:13:45 +0200 [thread overview]
Message-ID: <200408251713.45325.philipp.reisner@linbit.com> (raw)
Hi,
I tried to incooperate the comments of LMB and LGE. Please review:
after-pri-pri-now-sec-sec =
disconnect No automatic resynchronisation gets performed. One
node should drop its net-conf (preferable the
node that would become sync-target)
DEFAULT.
ass-older Auto sync source is the oder primary (curr.behaviour 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
pri-sees-sec-with-higher-gc =
disconnect (current behaviour)
ass-primary Auto sync source is the current primary
panic The current primary panics. The node with the
higher gc should take over.
Notes:
1) The disconnect actions cause the sync-target or the secondary
node to go into StandAllone state.
2) If two nodes in primary state try to connect one of them goes
into StandAllone state (=curr. behaviour)
3) As soon as the decission is takes the sync-target addopts the
GC of the sync source.
[ The whole algorith would also work if both would reset their
GCs to <0,0,0...> after the decission, but since we also
use the GC to tag the bitmap it is better the current way ]
Is this better than try2 ?
Should we improve the naming ? "ass" might not be the best choice.
Do you think that the naming is constent ?
Is it still ambiguous ?
-Philipp
--
: 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 :
next reply other threads:[~2004-08-25 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 15:13 Philipp Reisner [this message]
2004-08-26 8:27 ` [Drbd-dev] Summary (3rd try) 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=200408251713.45325.philipp.reisner@linbit.com \
--to=philipp.reisner@linbit.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.