From: Lon Hohberger <lhh@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 2/3] dlm_controld: full check for member changes
Date: Wed, 28 Sep 2011 16:30:17 -0400 [thread overview]
Message-ID: <4E8383D9.2040009@redhat.com> (raw)
In-Reply-To: <1317227848-8323-2-git-send-email-teigland@redhat.com>
On 09/28/2011 12:37 PM, David Teigland wrote:
> cman members are queried in response to a callback,
> and members sometimes leave and rejoin between queries
> (e.g. when they leave and rejoin before corosync
> detects they left.)
>
> This means that simply checking if a node is a member
> in consecutive queries sometimes misses events. We
> need to compare the incarnation numbers of members
> from consecutive queries to avoid this.
I was confused initially by the static ringid seq since its contents are
only used in the statechange() function, but it's consistent with other
variables and is useful for debugging, so ACK.
-- Lon
prev parent reply other threads:[~2011-09-28 20:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 16:37 [Cluster-devel] [PATCH 2/3] dlm_controld: full check for member changes David Teigland
2011-09-28 20:30 ` Lon Hohberger [this message]
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=4E8383D9.2040009@redhat.com \
--to=lhh@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;
as well as URLs for NNTP newsgroup(s).