From: Chuck Lever <chuck.lever@oracle.com>
To: Peter Staubach <staubach@redhat.com>
Cc: nfs@lists.sourceforge.net, Frank van Maarseveen <frankvm@frankvm.com>
Subject: Re: mount.nfs: chk_mountpoint()
Date: Thu, 30 Aug 2007 12:18:54 -0400 [thread overview]
Message-ID: <46D6EDEE.5060907@oracle.com> (raw)
In-Reply-To: <46D6EB44.7050600@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1446 bytes --]
Peter Staubach wrote:
> Chuck Lever wrote:
>> For the record, one downside to using automounter is the mount storm
>> that is caused when a distributed application starts up on multiple
>> clients requiring many NFS mount points on each client. This is one
>> reason some sites choose not to use automounter. "bg"s retry
>> behavior, though a kludge, is somewhat more friendly.
>
> If the application on each client is going to need many mount
> points, then how does "bg" do anything but increase the number
> of concurrent mount requests coming from each client, thus
> increasing the load?
"bg" has an exponential backoff, so the load increase isn't terribly
bothersome. It's the "bg" recovery mechanism that's useful here for
getting all the mount requests to be successful in a nondeterministic
environment.
I'm not arguing against automounter here; I'm just presenting a typical
use case that is common enough for us to pay some heed.
>> From my experience, generally mountd (on most any server
>> implementation) has been a scalability problem in these scenarios. It
>> can't handle more than a few requests per second.
>
> Perhaps we need to look at multithreading mountd? Ala Solaris?
Yes, although I was thinking of ways to make the client side more
friendly, say, by serializing mount requests to the same server, since
we don't have any influence on the scalability of mountd in non-Linux
NFS implementations.
[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 290 bytes --]
begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
url:http://oss.oracle.com/~cel
version:2.1
end:vcard
[-- Attachment #3: Type: text/plain, Size: 315 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #4: Type: text/plain, Size: 140 bytes --]
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-08-30 16:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 19:02 mount.nfs: chk_mountpoint() Chuck Lever
2007-08-23 12:50 ` Peter Staubach
2007-08-23 17:45 ` Chuck Lever
2007-08-23 18:22 ` Peter Staubach
2007-08-23 20:00 ` Chuck Lever
2007-08-23 20:12 ` Peter Staubach
2007-08-23 20:30 ` Chuck Lever
2007-08-23 20:49 ` Peter Staubach
2007-08-30 10:12 ` Frank van Maarseveen
2007-08-30 11:53 ` Peter Staubach
2007-08-30 16:01 ` Chuck Lever
2007-08-30 16:07 ` Peter Staubach
2007-08-30 16:18 ` Chuck Lever [this message]
2007-08-30 19:15 ` Talpey, Thomas
2007-08-30 21:11 ` Peter Staubach
2007-08-30 16:19 ` J. Bruce Fields
2007-08-30 16:24 ` Chuck Lever
2007-08-30 16:16 ` Frank van Maarseveen
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=46D6EDEE.5060907@oracle.com \
--to=chuck.lever@oracle.com \
--cc=frankvm@frankvm.com \
--cc=nfs@lists.sourceforge.net \
--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.