Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Lars Marowsky-Bree <lmb@suse.de>
To: High-Availability Linux Development List
	<linux-ha-dev@lists.linux-ha.org>,
	drbd-dev@lists.linbit.com
Subject: Re: [Linux-ha-dev] Re: [Drbd-dev] [RFC] Handling of internal split-brain in multiple state resources
Date: Fri, 24 Sep 2004 17:17:25 +0200	[thread overview]
Message-ID: <20040924151725.GY3927@marowsky-bree.de> (raw)
In-Reply-To: <200409201709.36849.philipp.reisner@linbit.com>

On 2004-09-20T17:09:36,
   Philipp Reisner <philipp.reisner@linbit.com> said:

> BTW, from the text I realized that hearbeat will monitor the resource (drbd).
> Probabely with calling the resource script with a new method. Basically
> hearbeat polls DRBD for an change in the connection state.
> 
> Would you like to have an active notification from DRBD ? 

Active notification is of course welcome. The CRM is event-based anyway,
so we could throw the event from drbd into the same machinery; that
would be a welcome addition.

Though not only connection state is interesting, but also the loss of
it's local disk.


Sincerely,
    Lars Marowsky-Brée <lmb@suse.de>

-- 
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX AG - A Novell company


  parent reply	other threads:[~2004-09-24 15:17 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   ` Lars Marowsky-Bree [this message]
2004-09-20 16:03 ` Lars Ellenberg
2004-09-21 12:58   ` Philipp Reisner
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=20040924151725.GY3927@marowsky-bree.de \
    --to=lmb@suse.de \
    --cc=drbd-dev@lists.linbit.com \
    --cc=linux-ha-dev@lists.linux-ha.org \
    /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