From: David Disseldorp <ddiss@suse.de>
To: Wei Jin <wjin.cn@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Osd failure detection
Date: Thu, 9 Nov 2017 12:03:18 +0100 [thread overview]
Message-ID: <20171109120318.1946caf2@suse.de> (raw)
In-Reply-To: <A80E9066-6266-49E2-9BD7-137E8136D6B9@gmail.com>
On Thu, 9 Nov 2017 17:43:04 +0800, Wei Jin wrote:
> Hi, List,
>
> From Luminous release, I noticed following information:
>
> "Some OSD failures are now detected almost immediately, whereas previously the heartbeat timeout (which defaults to 20 seconds) had to expire. This prevents IO from blocking for an extended period for failures where the host remains up but the ceph-osd process is no longer running."
I assume you're referring to the ECONNREFUSED-fast-fail functionality
added by Piotr Dałek.
> This is critical and we have no plan to upgrade to Luminous so far.
> Is there any plan to back port it Jewel? Or anybody know the related pr or patches? Maybe I could do it by myself.
It was backported to Jewel, alongside a bunch of other async messenger
fixes, and submitted via https://github.com/ceph/ceph/pull/13212 . IIRC,
there's still a small async messenger leak blocking the PR.
Cheers, David
next prev parent reply other threads:[~2017-11-09 11:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 9:43 Osd failure detection Wei Jin
2017-11-09 11:03 ` David Disseldorp [this message]
2017-11-09 12:13 ` Wei Jin
2017-11-09 12:25 ` Piotr Dałek
2017-11-09 14:19 ` Sage Weil
[not found] ` <A80E9066-6266-49E2-9BD7-137E8136D6B9-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-15 12:24 ` ceph-deploy failed to deploy osd randomly Wei Jin
2017-11-15 13:31 ` Wei Jin
[not found] ` <CAPpSHbUxYxekAOib+jE7y+7nQE44GkBwbrWN3FFaUh2Ev3ENvg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-16 13:08 ` Alfredo Deza
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=20171109120318.1946caf2@suse.de \
--to=ddiss@suse.de \
--cc=ceph-devel@vger.kernel.org \
--cc=wjin.cn@gmail.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.