All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sage Weil <sage@inktank.com>
To: Noah Watkins <jayhawk@cs.ucsc.edu>
Cc: Gregory Farnum <greg@inktank.com>,
	ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: CephFS mount delay
Date: Thu, 30 Aug 2012 13:39:36 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1208301339120.11149@cobra.newdream.net> (raw)
In-Reply-To: <CAPrxi58oZZ25BmcftEz+TgnHy70dPsHhivuFtXd6KkkF7NG8LQ@mail.gmail.com>

What about this:

diff --git a/src/client/Client.cc b/src/client/Client.cc
index 3333966..003e3f8 100644
--- a/src/client/Client.cc
+++ b/src/client/Client.cc
@@ -294,6 +294,7 @@ int Client::init()
   monclient->set_want_keys(CEPH_ENTITY_TYPE_MDS | CEPH_ENTITY_TYPE_OSD);
   monclient->sub_want("mdsmap", 0, 0);
   monclient->sub_want("osdmap", 0, CEPH_SUBSCRIBE_ONETIME);
+  monclient->renew_subs();
 
   // logger
   PerfCountersBuilder plb(cct, "client", l_c_first, l_c_last);


If that doesn't do it, can you reproduce with 'debug client = 20' and 
'debug monc = 20'?

Thanks!
sage



On Thu, 30 Aug 2012, Noah Watkins wrote:

> Here ya go:
> 
> https://dl.dropbox.com/u/7899675/client.log
> https://dl.dropbox.com/u/7899675/mds.a.log
> https://dl.dropbox.com/u/7899675/mds.b.log
> https://dl.dropbox.com/u/7899675/mds.c.log
> 
> - Noah
> 
> On Thu, Aug 30, 2012 at 1:15 PM, Sage Weil <sage@inktank.com> wrote:
> > I see that Server::handle_client_session is calling mdlog->flush(), so
> > it's a bit odd.  Can you generate a log with 'debug ms = 1' on the client
> > (and maybe mds) side?
> >
> > s
> >
> > On Thu, 30 Aug 2012, Noah Watkins wrote:
> >
> >> On Thu, Aug 30, 2012 at 1:06 PM, Gregory Farnum <greg@inktank.com> wrote:
> >> > On Thu, Aug 30, 2012 at 12:55 PM, Noah Watkins <jayhawk@cs.ucsc.edu> wrote:
> >> >> Using a tick interval of 1 drops the cost down to 3 seconds, but still
> >> >> a long time for running many unit tests that use fresh mounts.
> >> >
> >> > Are you using ceph-fuse or the kernel client? And how many of each daemon type?
> >>
> >> I'm using the C api, and there are 3 mon, 3 mds, 1 osd.
> >>
> >> > That said; I'm seeing broadly similar numbers ? with one of each
> >> > daemon (but otherwise the vstart defaults) "time sudo ceph-fuse mnt"
> >> > reports 3.1 seconds.
> >>
> >>
> 
> 

  reply	other threads:[~2012-08-30 20:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-30 18:50 CephFS mount delay Noah Watkins
2012-08-30 19:35 ` Sage Weil
2012-08-30 19:55   ` Noah Watkins
2012-08-30 20:06     ` Gregory Farnum
2012-08-30 20:09       ` Noah Watkins
2012-08-30 20:15         ` Sage Weil
2012-08-30 20:23           ` Gregory Farnum
2012-08-30 20:24           ` Noah Watkins
2012-08-30 20:39             ` Sage Weil [this message]
2012-08-30 20:46               ` Mike Ryan
2012-08-30 20:54                 ` Gregory Farnum
2012-08-30 20:59                   ` Sage Weil
2012-08-30 22:10               ` Noah Watkins
2012-08-30 22:17                 ` Gregory Farnum
2012-08-30 22:35                   ` Noah Watkins
2012-08-30 22:39                     ` Sage Weil
2012-08-30 22:44                       ` Noah Watkins
2012-08-30 22:47                         ` Gregory Farnum
2012-08-30 22:55                           ` Noah Watkins

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=alpine.DEB.2.00.1208301339120.11149@cobra.newdream.net \
    --to=sage@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=greg@inktank.com \
    --cc=jayhawk@cs.ucsc.edu \
    /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.