All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Decherf <kevin@kdecherf.com>
To: Gregory Farnum <greg@inktank.com>
Cc: Sam Lang <sam.lang@inktank.com>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
	support@clever-cloud.com
Subject: Re: Crash and strange things on MDS
Date: Tue, 26 Feb 2013 18:57:42 +0100	[thread overview]
Message-ID: <20130226175742.GE16091@kdecherf.com> (raw)
In-Reply-To: <CAPYLRzgkR61eFuGU_NdL88bJvOD2em+TMO7g1g+X3RTFAZvY5Q@mail.gmail.com>

On Tue, Feb 19, 2013 at 05:09:30PM -0800, Gregory Farnum wrote:
> On Tue, Feb 19, 2013 at 5:00 PM, Kevin Decherf <kevin@kdecherf.com> wrote:
> > On Tue, Feb 19, 2013 at 10:15:48AM -0800, Gregory Farnum wrote:
> >> Looks like you've got ~424k dentries pinned, and it's trying to keep
> >> 400k inodes in cache. So you're still a bit oversubscribed, yes. This
> >> might just be the issue where your clients are keeping a bunch of
> >> inodes cached for the VFS (http://tracker.ceph.com/issues/3289).
> >
> > Thanks for the analyze. We use only one ceph-fuse client at this time
> > which makes all "high-load" commands like rsync, tar and cp on a huge
> > amount of files. Well, I will replace it by the kernel client.
> 
> Oh, that bug is just an explanation of what's happening; I believe it
> exists in the kernel client as well.

After setting the mds cache size to 900k, storms are gone.
However we continue to observe high latency on some clients (always the
same clients): each IO takes between 40 and 90ms (for example with
Wordpress, it takes ~20 seconds to load all needed files...).
With a non-laggy client, IO requests take less than 1ms.

-- 
Kevin Decherf - @Kdecherf
GPG C610 FE73 E706 F968 612B E4B2 108A BD75 A81E 6E2F
http://kdecherf.com

  reply	other threads:[~2013-02-26 17:58 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04 18:01 Crash and strange things on MDS Kevin Decherf
2013-02-11 13:05 ` Kevin Decherf
2013-02-11 17:00   ` Sam Lang
2013-02-11 18:54     ` Kevin Decherf
2013-02-11 20:25       ` Gregory Farnum
2013-02-11 22:24         ` Kevin Decherf
2013-02-11 22:47           ` Gregory Farnum
2013-02-11 23:33             ` Kevin Decherf
2013-02-13 11:47         ` Kevin Decherf
2013-02-13 18:19           ` Gregory Farnum
2013-02-16  1:02             ` Kevin Decherf
2013-02-16 17:36               ` Sam Lang
2013-02-16 18:24                 ` Kevin Decherf
2013-02-19 18:15                   ` Gregory Farnum
2013-02-20  1:00                     ` Kevin Decherf
2013-02-20  1:09                       ` Gregory Farnum
2013-02-26 17:57                         ` Kevin Decherf [this message]
2013-02-26 18:10                           ` Gregory Farnum
2013-02-26 19:58                             ` Kevin Decherf
2013-02-26 20:26                               ` Gregory Farnum
2013-02-26 21:57                                 ` Kevin Decherf
2013-02-26 21:58                                   ` Gregory Farnum
2013-02-27  0:03                                     ` Yan, Zheng 
2013-02-27  0:14                                       ` Sage Weil
     [not found]                                     ` <20130227004923.GQ16091@kdecherf.com>
     [not found]                                       ` <CAPYLRzhbygkA9=DkVr474Nw8AOC2hAFG-1D6uS4WyfR=kUBXWQ@mail.gmail.com>
     [not found]                                         ` <20130308232943.GA2197@kdecherf.com>
     [not found]                                           ` <20130308232943.GA2197-fShu9kyPgSlWk0Htik3J/w@public.gmane.org>
2013-03-15 20:32                                             ` Greg Farnum
     [not found]                                               ` <ECAA10260D284057A52D78127F8634A8-4GqslpFJ+cxBDgjK7y7TUQ@public.gmane.org>
2013-03-15 22:40                                                 ` Marc-Antoine Perennou
2013-03-15 22:53                                                   ` Greg Farnum

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=20130226175742.GE16091@kdecherf.com \
    --to=kevin@kdecherf.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=greg@inktank.com \
    --cc=sam.lang@inktank.com \
    --cc=support@clever-cloud.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.