From: David Disseldorp <ddiss@suse.de>
To: ceph-devel <ceph-devel@vger.kernel.org>
Subject: udev remove events to mark OSD down/out on disk-pull
Date: Wed, 16 Nov 2016 03:30:42 +0100 [thread overview]
Message-ID: <20161116033042.68eee001@suse.de> (raw)
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.
For the disk-pull case, this should be relatively easy to speed up
by handling the remove event in 95-ceph-osd.rules with an appropriate
osd down/out PDU. The problem then becomes maintaining consistent
information in the udev database (all stashed via IMPORT{program}):
- cluster / OSD ids
- appropriate cephx creds
Before I hack something up for this, I'm interested in what others
think, and whether anyone has already gone down this path. I seem to
recall someone attempting to change the ceph-osd behaviour on I/O
error at some stage.
Cheers, David
next reply other threads:[~2016-11-16 2:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 2:30 David Disseldorp [this message]
2016-11-16 7:05 ` udev remove events to mark OSD down/out on disk-pull Loic Dachary
2016-11-16 12:57 ` David Disseldorp
2016-11-16 14:50 ` Sage Weil
2016-11-16 15:16 ` David Disseldorp
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=20161116033042.68eee001@suse.de \
--to=ddiss@suse.de \
--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