From: Daniel Phillips <phillips@istop.com>
To: Lars Marowsky-Bree <lmb@suse.de>
Subject: Re: [PATCH 1b/7] dlm: core locking
Date: Wed, 27 Apr 2005 22:52:55 -0400
User-Agent: KMail/1.7
Cc: David Teigland <teigland@redhat.com>, Steven Dake <sdake@mvista.com>,
       linux-kernel@vger.kernel.org, akpm@osdl.org
References: <20050425165826.GB11938@redhat.com> <20050427030217.GA9963@redhat.com> <20050427134142.GZ4431@marowsky-bree.de>
In-Reply-To: <20050427134142.GZ4431@marowsky-bree.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200504272252.55525.phillips@istop.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 891
Lines: 21

On Wednesday 27 April 2005 09:41, Lars Marowsky-Bree wrote:
> ...I assume that the delivery of a "node down" membership event
> implies that said node also has been fenced.
>
> So we can't deliver it raw membership events. Noted.

Just to pick a nit: there is no way to be sure a membership event might not 
still be on the way to the dead node, however the rest of the cluster knows 
the node is dead and can ignore it, in theory.  (In practice, only (g)dlm and 
gfs are well glued into the cman membership protocol, and other components, 
e.g., cluster block devices and applications, need to be looked at with 
squinty eyes.)

Regards,

Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/