From: Stefan Priebe <s.priebe@profihost.ag>
To: Sage Weil <sage@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: waiting for sub ops
Date: Sun, 13 May 2012 20:04:32 +0200 [thread overview]
Message-ID: <4FAFF7B0.2030400@profihost.ag> (raw)
In-Reply-To: <Pine.LNX.4.64.1205121714120.21796@cobra.newdream.net>
Hi Sage,
Am 13.05.2012 02:15, schrieb Sage Weil:
> On Fri, 11 May 2012, Stefan Priebe - Profihost AG wrote:
>> Hi,
>>
>> while doing some stress testing with bonnie++ i'm seeing always these
>> messages accross all osd's here is just an example for osd.2.
>>
>> All machines are connected with 2x 1Gbit/s bonding mode 6 to a HP switch.
>
> These are just telling you that some operations are taking> 30 seconds.
> The 'waiting for sub ops' means that it is waiting for the write/update to
> be acked by other replicas. Either there is some load imbalance (some
> osds are more busy than others), or everyone is similarly loaded and the
> request queues are just long across the board.
mhm but there must be something wrong in my testsetup.
1.) th osd bench shows 150MB/s per osd
2.) iperf shows constant 930Mbit/s per eth
3.) when i write 16GB with dd to the ceph mount i see spikes to 450Mbit/
and drops to 90kb/s for long periods of time. The overall dd speed is
then 40Mbit/s
4.) the speed drops to 90kb/s while seeing the
"[WRN] slow request received at 2012-05-13 20:01:55.227811:
osd_op(client.4102.1:38432 10000000004.000003ae [write 0~4194304]
0.5f4dfca8 snapc 1=[]) currently waiting for sub ops"
messages.
The client shows this in dmesg:
[2012-05-13 19:55:26] libceph: tid 38132 timed out on osd2, will reset osd
[2012-05-13 19:55:46] libceph: tid 38400 timed out on osd0, will reset osd
[2012-05-13 19:56:31] libceph: tid 38886 timed out on osd2, will reset osd
greets and thanks
Stefan
next prev parent reply other threads:[~2012-05-13 18:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 7:02 waiting for sub ops Stefan Priebe - Profihost AG
2012-05-11 13:25 ` Stefan Priebe - Profihost AG
2012-05-13 0:13 ` Sage Weil
2012-05-13 0:15 ` Sage Weil
2012-05-13 18:04 ` Stefan Priebe [this message]
2012-05-14 4:28 ` Sage Weil
2012-05-14 6:36 ` Stefan Priebe - Profihost AG
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=4FAFF7B0.2030400@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox