From: Olaf Kirch <okir@lst.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [NFS] [PATCH 3/4 Revised] NLM - kernel lockd-statd changes
Date: Tue, 17 Apr 2007 16:51:35 +0200 [thread overview]
Message-ID: <200704171651.36497.okir@lst.de> (raw)
In-Reply-To: <4624CA93.4040307@redhat.com>
On Tuesday 17 April 2007 15:24, Wendy Cheng wrote:
> > I think in term of correctness, it's better to send an SM_NOTIFY
> > for each IP associated with such a set, anyway.
> >
>
> That's exactly what we have been proposing... :) .. We'll rely heavily
> on HA callout program to tell us which client uses which (server)
> floating IP.
Correct me if I'm wrong, but it seems your patch records every IP
used by the client, rather than the *all* the IPs related to the set of
file systems being moved. So if there are several IPs for this set, you
will end up sending notifications only from those the client happened
to have talked to.
My point was, you move a set of file systems A, B and C, with
IPs X, Y, Z. You know what the addresses are, so from a
robustness point of view your best bet is to send SM_NOTIFY
messages from IPs X, Y, Z, regardless of whether the client has
been talking to all of them, or just one.
Olaf
--
Olaf Kirch | --- o --- Nous sommes du soleil we love when we play
okir at lst.de | / | \ sol.dhoop.naytheet.ah kin.ir.samse.qurax
next prev parent reply other threads:[~2007-04-17 14:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 21:52 [Cluster-devel] [PATCH 3/4 Revised] NLM - kernel lockd-statd changes Wendy Cheng
2007-04-10 9:10 ` [Cluster-devel] Re: [NFS] " Olaf Kirch
2007-04-10 14:41 ` Lon Hohberger
2007-04-10 15:00 ` Wendy Cheng
2007-04-10 18:16 ` Wendy Cheng
[not found] ` <message from Olaf Kirch on Tuesday April 10>
2007-04-11 4:50 ` Neil Brown
2007-04-13 19:16 ` Lon Hohberger
2007-04-13 19:31 ` Wendy Cheng
2007-04-17 11:52 ` Olaf Kirch
2007-04-17 13:24 ` Wendy Cheng
2007-04-17 14:51 ` Olaf Kirch [this message]
2007-04-17 15:09 ` Wendy Cheng
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=200704171651.36497.okir@lst.de \
--to=okir@lst.de \
/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).