From: John Simon <tzzhc4@yahoo.com>
To: Peter Staubach <staubach@redhat.com>
Cc: autofs@linux.kernel.org
Subject: Re: Has replicated mount failover been implemented?
Date: Thu, 11 Oct 2007 20:18:39 -0700 (PDT) [thread overview]
Message-ID: <430834.18700.qm@web81808.mail.mud.yahoo.com> (raw)
In-Reply-To: <470E7FDB.5090202@redhat.com>
We have two pairs of VCS HA-NFS servers (one in each
data center), so each entry in auto_appl is the VIP
for the HA pair. Should one portion of the cluster in
the data center local to the compute engines fail it
will just fail over to the other cluster node and
client-side failover would not be used. If however the
entire cluster fails or is unavailable for whatever
reason the duplicate VCS HA-NFS server in the other
data center resumes serving data, albeit at a slightly
slower rate due to latency over the MAN. This site to
site failover is where we currently depend on Solaris
client-side failover.
--- Peter Staubach <staubach@redhat.com> wrote:
> I don't think that I understand what the client side
> failover
> of Solaris was being used for in this configuration.
> If the
> server is truly HA, then shouldn't the NFS service
> be able to
> failover from one server to the next with minimal
> interruption
> on the clients?
>
> The Solaris client side failover required relooking
> up all
> file handles which referred to the dead server, so
> it wasn't
> cheap either.
>
> Thanx...
>
> ps
>
____________________________________________________________________________________
Need a vacation? Get great deals
to amazing places on Yahoo! Travel.
http://travel.yahoo.com/
next prev parent reply other threads:[~2007-10-12 3:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 6:28 Has replicated mount failover been implemented? John Simon
2007-10-11 6:59 ` Ian Kent
2007-10-11 18:50 ` John Simon
2007-10-11 19:21 ` Jeff Moyer
2007-10-11 19:56 ` Peter Staubach
2007-10-12 3:18 ` John Simon [this message]
2007-10-12 11:35 ` Peter Staubach
2007-10-11 22:39 ` Todd Denniston
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=430834.18700.qm@web81808.mail.mud.yahoo.com \
--to=tzzhc4@yahoo.com \
--cc=autofs@linux.kernel.org \
--cc=staubach@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.