From: Mark Nelson <mark.nelson@inktank.com>
To: Alexandre DERUMIER <aderumier@odiso.com>
Cc: David Blundell <David.Blundell@100percentit.com>,
ceph-devel@vger.kernel.org
Subject: Re: Slow request warnings on 0.48
Date: Thu, 05 Jul 2012 12:58:27 -0500 [thread overview]
Message-ID: <4FF5D5C3.80207@inktank.com> (raw)
In-Reply-To: <44469a6e-79a3-4eaa-be25-c47192c8fc80@mailpro>
On 07/04/2012 11:58 AM, Alexandre DERUMIER wrote:
> Hi, I see same messages here after upgrade to 0.48.
>
> with random write benchmark.
>
> I have more lags than before with 0.47 (but disks are at 100% usage, so can't tell if it's normal or not)
>
>
> ----- Mail original -----
>
> De: "David Blundell"<David.Blundell@100percentit.com>
> À: ceph-devel@vger.kernel.org
> Envoyé: Mercredi 4 Juillet 2012 18:53:02
> Objet: Slow request warnings on 0.48
>
> I have three servers running mon and osd using Ubuntu 12.04 that I have been testing with RADOS storing RBD KVM instances
>
> 0.47.3 worked extremely well (once I got over a few btrfs issues). The same servers running 0.48 give a large number of "[WRN] slow request" messages whenever I generate a lot of random IO in the KVM instances using iozone. The slow responses eventually leads to disk timeouts on the KVM instances.
>
> I have erased the osds and recreated on new btrfs volumes with the same result.
>
> I have also tried switching to xfs using mkfs.xfs -n size=64k with noatime, inode64,delaylog,logbufs=8,logbsize=256k
>
> Xfs gives the same result - the iozone tests run fine until the random IO starts and then there are lots of slow request warnings.
>
> Does anyone have any ideas about the best place to start troubleshooting / debugging?
>
> Thanks,
>
> David
Hi David and Alexandre,
Does this only happen with random writes or also sequential writes? If
it happens with sequential writes as well, does it happen with rados bench?
--
Mark Nelson
Performance Engineer
Inktank
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-07-05 17:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 16:53 Slow request warnings on 0.48 David Blundell
2012-07-04 16:58 ` Alexandre DERUMIER
2012-07-04 18:59 ` Gregory Farnum
2012-07-04 22:03 ` David Blundell
2012-07-05 17:58 ` Mark Nelson [this message]
2012-07-05 18:16 ` David Blundell
2012-07-05 18:33 ` Alexandre DERUMIER
2012-07-05 18:43 ` David Blundell
2012-07-05 19:49 ` Mark Nelson
2012-07-05 20:21 ` Samuel Just
2012-07-05 22:15 ` David Blundell
-- strict thread matches above, loose matches on Subject: below --
2012-07-19 10:48 Matthew Richardson
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=4FF5D5C3.80207@inktank.com \
--to=mark.nelson@inktank.com \
--cc=David.Blundell@100percentit.com \
--cc=aderumier@odiso.com \
--cc=ceph-devel@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