From: Stefan Priebe <s.priebe@profihost.ag>
To: Sage Weil <sage@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: maintanance on osd host
Date: Tue, 26 Feb 2013 20:44:42 +0100 [thread overview]
Message-ID: <512D10AA.2020906@profihost.ag> (raw)
In-Reply-To: <alpine.DEB.2.00.1302260922510.4819@cobra.newdream.net>
Hi Sage,
Am 26.02.2013 18:24, schrieb Sage Weil:
> On Tue, 26 Feb 2013, Stefan Priebe - Profihost AG wrote:
>> But that redults in a 1-3s hickup for all KVM vms. This is not what I want.
>
> You can do
>
> kill $pid
> ceph osd down $osdid
>
> (or even reverse the order, if the sequence is quick enough) to avoid
> waiting for the failure detection delay. But if the OSDs are going down,
> then the peering has to happen one way or another.
But exaclty this results in starting backfill immediatly. My idea was to
first mark the osd down so the mon knows about this fact. So no I/O is
stalled. And then reboot the whole host but exactly this does not work
like expected as backfilling is starting immediatly after setting the
osd to down ;-(
Greets,
Stefan
next prev parent reply other threads:[~2013-02-26 19:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 14:56 maintanance on osd host Stefan Priebe - Profihost AG
[not found] ` <512CCD19.7010509-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2013-02-26 15:09 ` Andrey Korolyov
2013-02-26 17:06 ` Sage Weil
2013-02-26 17:22 ` Stefan Priebe - Profihost AG
2013-02-26 17:24 ` Sage Weil
2013-02-26 19:44 ` Stefan Priebe [this message]
2013-02-26 20:02 ` Sage Weil
2013-02-26 20:27 ` Gregory Farnum
2013-02-27 7:37 ` Stefan Priebe - Profihost AG
2013-02-28 16:14 ` Gregory Farnum
2013-03-01 19:40 ` John Wilkins
2013-03-01 20:38 ` Sylvain Munaut
2013-03-01 23:10 ` John Wilkins
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=512D10AA.2020906@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@inktank.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.