public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars Marowsky-Bree <lmb@suse.de>
To: Daniel Phillips <phillips@istop.com>
Cc: Daniel McNeil <daniel@osdl.org>,
	David Teigland <teigland@redhat.com>,
	Steven Dake <sdake@mvista.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	Patrick Caulfield <pcaulfie@redhat.com>
Subject: Re: [PATCH 1b/7] dlm: core locking
Date: Mon, 2 May 2005 22:51:35 +0200	[thread overview]
Message-ID: <20050502205135.GC4722@marowsky-bree.de> (raw)
In-Reply-To: <200504300712.46835.phillips@istop.com>

On 2005-04-30T07:12:46, Daniel Phillips <phillips@istop.com> wrote:

> process.  And obviously, there already is some reliable starting point or 
> cman would not work.  So let's just expose that and have a better cluster 
> stack.

Most memberships internally construct such a fixed starting point from
voting or other 'chatty' techniques.

This is exposed by the membership (providing all nodes in the same order
on all nodes), however the node level membership does not necessarily
reflect the service/application level membership. So to get it right,
you essentially have to run such an algorithm at that level again too.

True enough it would be helpful if the group membership service provided
such, but here we're at the node level.

> But note that it _can_ use the oldest cluster member as a recovery
> master, or to designate a recovery master.  It can, and should - there
> is no excuse for making this any more complex than it needs to be.

The oldest node might not be running that particular service, or it
might not be healthy. To figure that out, you need to vote.

This is straying a bit from LKML issues, maybe it ought to be moved to
one of the clustering lists.


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

-- 
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business	 -- Charles Darwin
"Ignorance more frequently begets confidence than does knowledge"


  reply	other threads:[~2005-05-02 21:01 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-25 16:58 [PATCH 1b/7] dlm: core locking David Teigland
2005-04-25 18:34 ` Nikita Danilov
2005-04-25 20:44   ` Daniel Phillips
2005-04-25 22:27     ` Nikita Danilov
2005-04-26  1:34       ` Daniel Phillips
2005-04-25 20:41 ` Jesper Juhl
2005-04-26  5:00   ` Daniel Phillips
2005-04-25 21:54 ` Steven Dake
2005-04-26  5:49   ` David Teigland
2005-04-26 17:40     ` Steven Dake
2005-04-26 22:24       ` Daniel Phillips
2005-04-26 23:04         ` Steven Dake
2005-04-27  0:53           ` Daniel Phillips
2005-04-27  1:50             ` Steven Dake
2005-04-27  4:21               ` Daniel Phillips
2005-04-27  3:02       ` David Teigland
2005-04-27 13:41         ` Lars Marowsky-Bree
2005-04-27 14:26           ` David Teigland
2005-04-28 12:33             ` Lars Marowsky-Bree
2005-04-28 16:39               ` Daniel McNeil
2005-04-28 16:45                 ` Lars Marowsky-Bree
2005-04-29  8:25                   ` Daniel Phillips
2005-05-02 20:45                     ` Lars Marowsky-Bree
2005-05-02 23:23                       ` Daniel Phillips
2005-04-29  4:01                 ` David Teigland
2005-04-29 22:58                   ` Daniel McNeil
2005-04-30  4:29                     ` David Teigland
2005-04-30  9:09                     ` Daniel Phillips
2005-04-30 10:32                       ` Lars Marowsky-Bree
2005-04-30 11:12                         ` Daniel Phillips
2005-05-02 20:51                           ` Lars Marowsky-Bree [this message]
2005-05-02 22:21                             ` Daniel Phillips
2005-05-05 12:25                       ` Stephen C. Tweedie
2005-05-05 12:40                         ` copy_to_user question linux
2005-05-05 13:13                           ` Richard B. Johnson
2005-05-05 19:29                         ` [PATCH 1b/7] dlm: core locking Daniel Phillips
2005-04-28  2:52           ` Daniel Phillips
2005-04-28 12:37             ` Lars Marowsky-Bree
2005-04-28 23:43               ` Daniel Phillips
2005-04-28  6:49           ` Daniel Phillips
2005-04-28 12:55             ` Lars Marowsky-Bree
2005-04-29  0:26               ` Daniel Phillips
2005-04-29  2:52                 ` David Teigland
2005-04-29  3:49                   ` Daniel Phillips
2005-05-02 21:00                     ` Lars Marowsky-Bree
2005-05-03  2:54                       ` David Teigland
2005-04-27 12:33 ` Domen Puncer
2005-04-27 13:30   ` David Teigland

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=20050502205135.GC4722@marowsky-bree.de \
    --to=lmb@suse.de \
    --cc=akpm@osdl.org \
    --cc=daniel@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pcaulfie@redhat.com \
    --cc=phillips@istop.com \
    --cc=sdake@mvista.com \
    --cc=teigland@redhat.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