All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory Farnum <greg@inktank.com>
To: Alexandre DERUMIER <aderumier@odiso.com>,
	David Blundell <David.Blundell@100percentit.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Slow request warnings on 0.48
Date: Wed, 4 Jul 2012 11:59:55 -0700	[thread overview]
Message-ID: <D9AB48B599C2406EB9C62F237DC58FF1@inktank.com> (raw)
In-Reply-To: <44469a6e-79a3-4eaa-be25-c47192c8fc80@mailpro>

That's odd — there isn't too much that went into the OSD between 0.47 and 0.48 that I can think of, and most of that only impact OSDs when they go through bootup. What does ceph -s display — are all the PGs healthy?  
-Greg


On Wednesday, July 4, 2012 at 9: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 (mailto:David.Blundell@100percentit.com)>  
> À: ceph-devel@vger.kernel.org (mailto: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  
> --  
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in  
> the body of a message to majordomo@vger.kernel.org (mailto:majordomo@vger.kernel.org)  
> More majordomo info at http://vger.kernel.org/majordomo-info.html  
>  
>  
>  
> --  
>  
> --  
>  
>  
>  
>  
> Alexandre D e rumier  
>  
> Ingénieur Systèmes et Réseaux  
>  
>  
> Fixe : 03 20 68 88 85  
>  
> Fax : 03 20 68 90 88  
>  
>  
> 45 Bvd du Général Leclerc 59100 Roubaix  
> 12 rue Marivaux 75002 Paris  
>  
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org (mailto:majordomo@vger.kernel.org)
> More majordomo info at http://vger.kernel.org/majordomo-info.html



--
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

  reply	other threads:[~2012-07-04 18:59 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 [this message]
2012-07-04 22:03     ` David Blundell
2012-07-05 17:58   ` Mark Nelson
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
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=D9AB48B599C2406EB9C62F237DC58FF1@inktank.com \
    --to=greg@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 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.