From: David Disseldorp <ddiss@suse.de>
To: Sage Weil <sage@newdream.net>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: udev remove events to mark OSD down/out on disk-pull
Date: Wed, 16 Nov 2016 16:16:02 +0100 [thread overview]
Message-ID: <20161116161602.7d5ff898@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.11.1611161448100.8814@piezo.us.to>
On Wed, 16 Nov 2016 14:50:30 +0000 (UTC), Sage Weil wrote:
> On Wed, 16 Nov 2016, David Disseldorp wrote:
> > Hi,
> >
> > I'm currently looking at ways to speed up OSD down/out notifications
> > for disk-pull events, and was investigating using udev remove events
> > for this.
> >
> > IIUC, the outage currently propagates through to the mons via OSD device
> > I/O error -> filestore I/O error -> ceph-osd ceph_abort() -> heartbeat
> > failure.
>
> We just merged (post-jewel) a change that makes connection refused events
> trigger an immediate mark-down of the peer OSD. I think this will have
> the same effect, as long as the ceph-osd process is killed in a timely
> manner. Have you tried it? I'd suggest making sure that it's not
> sufficient before investing too much time into a udev-based approach...
>
> See a033dc6f5b4cef357db6f5951062d680e880ba0e
Looks much cleaner than handling this in udev. I'll test this with
Jewel and follow up - thanks Sage!
Cheers, David
prev parent reply other threads:[~2016-11-16 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 2:30 udev remove events to mark OSD down/out on disk-pull David Disseldorp
2016-11-16 7:05 ` Loic Dachary
2016-11-16 12:57 ` David Disseldorp
2016-11-16 14:50 ` Sage Weil
2016-11-16 15:16 ` David Disseldorp [this message]
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=20161116161602.7d5ff898@suse.de \
--to=ddiss@suse.de \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@newdream.net \
/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