All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mark.nelson@inktank.com>
To: Sage Weil <sage@inktank.com>
Cc: "Chen, Xiaoxi" <xiaoxi.chen@intel.com>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
	"ceph-users@ceph.com" <ceph-users@ceph.com>
Subject: Re: [ceph-users] OSD state flipping when cluster-network in high utilization
Date: Tue, 14 May 2013 10:35:33 -0500	[thread overview]
Message-ID: <519259C5.3000109@inktank.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1305140828550.22973@cobra.newdream.net>

On 05/14/2013 10:30 AM, Sage Weil wrote:
> On Tue, 14 May 2013, Chen, Xiaoxi wrote:
>>
>> Hi
>>
>>    We are suffering our OSD flipping between up and down ( OSD X be voted to
>> down due to 3 missing ping, and after a while it tells the monitor ?map xxx
>> wrongly mark me down? ). Because we are running sequential write performance
>> test on top of RBDs, and the cluster network nics is really in high
>> utilization (8Gb/s+ for a 10Gb network).
>>
>>           Is this a expected behavior ? or how can I prevent this happen?
>
> You an increase the heartbeat grace period.  The pings are handled by a
> separate thread on the backside interface (if there is one).  If you are
> missing pings then the network or scheduler is preventing those (small)
> messages from being processed (there is almost no lock contention in that
> path).  Which means it really is taking ~20 seconds or wahtever to handle
> those messages.  It's really a questin of how unresponsive you want to
> permit the OSDs to be before you consider it a failure..
>
> sage
>
>

It might be worth testing out how long pings or other network traffic 
are taking during these tests.  There may be some tcp tunning you can do 
here, or even consider using a separate network for the mons.

Mark

  reply	other threads:[~2013-05-14 15:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14  8:56 OSD state flipping when cluster-network in high utilization Chen, Xiaoxi
2013-05-14 15:30 ` [ceph-users] " Sage Weil
2013-05-14 15:35   ` Mark Nelson [this message]
     [not found]     ` <519259C5.3000109-4GqslpFJ+cxBDgjK7y7TUQ@public.gmane.org>
2013-05-14 23:13       ` Chen, Xiaoxi
     [not found]         ` <6AC1548D-DE2C-4E71-AC73-3903B57C76C6-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2013-05-14 23:22           ` Sage Weil
     [not found]             ` <alpine.DEB.2.00.1305141620410.12954-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2013-05-15  3:23               ` Chen, Xiaoxi
     [not found]                 ` <6F3FA899187F0043BA1827A69DA2F7CC0145F746-0J0gbvR4kTiiAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-05-15  3:40                   ` Sage Weil
     [not found]                     ` <alpine.DEB.2.00.1305142039520.23131-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2013-05-15 12:53                       ` Chen, Xiaoxi
     [not found]                         ` <alpine.DEB.2.00.1305150851190.14301@cobra.newdream.net>
2013-05-23  2:08                           ` [ceph-users] " Chen, Xiaoxi
2013-05-15 15:05                   ` Jim Schutt
2013-05-15 15:12                     ` [ceph-users] " Chen, Xiaoxi
2013-05-15 15:38                       ` Jim Schutt
2013-05-15  0:52   ` Wales Wang

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=519259C5.3000109@inktank.com \
    --to=mark.nelson@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ceph-users@ceph.com \
    --cc=sage@inktank.com \
    --cc=xiaoxi.chen@intel.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.