From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] [RFC] Handling of internal split-brain in multiple state resources
Date: Tue, 21 Sep 2004 14:58:28 +0200 [thread overview]
Message-ID: <200409211458.28093.philipp.reisner@linbit.com> (raw)
In-Reply-To: <bssllma/59fU4MzbzTYqnts=lge@web.de>
[...]
> the algorithm within the CRM is
> res = some replicating resource which no longer sees its peer
> if res is in master state
> fence the peer (by marking it outdated or stonithing it)
> tell res about that, and to continue
> if res is in passive state
> trigger immediate monitoring of the peer(s),
> but otherwise do nothing
Seems that we have exactly the same imagination about this...
-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 prev parent reply other threads:[~2004-09-21 12:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 18:55 [Drbd-dev] [RFC] Handling of internal split-brain in multiple state resources Lars Marowsky-Bree
2004-09-20 15:09 ` Philipp Reisner
2004-09-20 15:36 ` Lars Ellenberg
2004-09-24 15:17 ` [Linux-ha-dev] " Lars Marowsky-Bree
2004-09-20 16:03 ` Lars Ellenberg
2004-09-21 12:58 ` Philipp Reisner [this message]
2004-09-24 15:15 ` [Linux-ha-dev] " 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=200409211458.28093.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox