From: Josh Durgin <josh.durgin@inktank.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: Sage Weil <sage@inktank.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: endless flying slow requests
Date: Thu, 15 Nov 2012 00:18:40 -0800 [thread overview]
Message-ID: <50A4A560.3010406@inktank.com> (raw)
In-Reply-To: <50A4A351.8020506@profihost.ag>
On 11/15/2012 12:09 AM, Stefan Priebe - Profihost AG wrote:
> Am 14.11.2012 15:59, schrieb Sage Weil:
>> Hi Stefan,
>>
>> I would be nice to confirm that no clients are waiting on replies for
>> these requests; currently we suspect that the OSD request tracking is the
>> buggy part. If you query the OSD admin socket you should be able to dump
>> requests and see the client IP, and then query the client.
>>
>> Is it librbd? In that case you likely need to change the config so that
>> it is listening on an admin socket ('admin socket = path').
>
> Yes it is. So i have to specify admin socket at the KVM host? How do i
> query the admin socket for requests?
Yes, add 'admin socket = /path/to/admin/socket' to the [client] section
in ceph.conf, and when a guest is running, show outstanding requests
with:
ceph --admin-daemon /path/to/admin/socket objecter_requests
Josh
next prev parent reply other threads:[~2012-11-15 8:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 9:12 endless flying slow requests Stefan Priebe - Profihost AG
2012-11-14 14:59 ` Sage Weil
2012-11-15 8:09 ` Stefan Priebe - Profihost AG
2012-11-15 8:18 ` Josh Durgin [this message]
2012-11-15 14:58 ` Sage Weil
2012-11-28 1:51 ` Sage Weil
2012-11-28 7:23 ` Stefan Priebe - Profihost AG
2012-11-28 7:47 ` Andrey Korolyov
2012-11-28 21:11 ` Samuel Just
2012-11-28 21:12 ` Samuel Just
2012-11-28 21:52 ` Moore, Shawn M
2012-11-28 22:04 ` Andrey Korolyov
2012-12-01 5:06 ` Samuel Just
2012-12-02 3:18 ` Sage Weil
2012-12-02 22:02 ` Samuel Just
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=50A4A560.3010406@inktank.com \
--to=josh.durgin@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=s.priebe@profihost.ag \
--cc=sage@inktank.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.