linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daire Byrne <daire@dneg.com>
To: linux-nfs <linux-nfs@vger.kernel.org>
Subject: rpc.mountd & manage-gids behaviour change?
Date: Thu, 24 Aug 2023 18:39:19 +0100	[thread overview]
Message-ID: <CAPt2mGOcf+y1acYqzB+a3aZOJM0kE=FcWr-Xs15ECswGXP8-yA@mail.gmail.com> (raw)

Hi,

We have lots of Linux storage servers running combinations of RHEL7,
RHEL8 and more recently RHEL9. We also use "manage-gids" and have lots
of groups of users and apply permissions to directories on the
exported filesystems.

We also use sssd and AD/LDAP on these storage servers to resolve the
groups and do the user lookups. This setup has worked great for our
needs for many years but we have noticed a change in RHEL9 which
results in many more uid/gid lookups hitting our LDAP servers.

It seems like with RHEL7 & 8 era kernels and nfs-utils, sssd/nss would
receive a single request from rpc.mountd whereas with RHEL9 we now get
duplicated requests for each rpc.mountd thread (8 by default) even for
a single client mount. So 8 uid/gid requests hit sssd at the same
time, and because it's not in cache, all those 8 requests go out over
the wire to our AD server.

So for lookups not in the cache, we have 8 times more requests hitting
our LDAP servers. Not to mention that sssd sometimes crashes or loses
connectivity with the LDAP server with this increased load.

I had a look through the changes for linux-nfs but nothing jumped out
at me in that time frame (other than code to make exportd
multi-threaded). Does anyone have any ideas where this change of
behaviour might be coming from?

RHEL9: nfs-utils-2.5.4
RHEL8: nfs-utils-2.3.3

Cheers,

Daire

             reply	other threads:[~2023-08-24 17:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24 17:39 Daire Byrne [this message]
2023-09-08  8:32 ` rpc.mountd & manage-gids behaviour change? Daire Byrne

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='CAPt2mGOcf+y1acYqzB+a3aZOJM0kE=FcWr-Xs15ECswGXP8-yA@mail.gmail.com' \
    --to=daire@dneg.com \
    --cc=linux-nfs@vger.kernel.org \
    /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).