All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Kunz <chrislist@de-punkt.de>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Best practice with 0.48.2 to take a node into maintenance
Date: Mon, 03 Dec 2012 20:49:23 +0100	[thread overview]
Message-ID: <50BD0243.2050109@de-punkt.de> (raw)
In-Reply-To: <50BCFA2F.9070603@inktank.com>

Am 03.12.12 20:14, schrieb Josh Durgin:
> On 12/03/2012 11:05 AM, Oliver Francke wrote:
>> Hi *,
>>
>> well, even if 0.48.2 is really stable and reliable, it is not
>> everytime the case with linux kernel. We have a couple of nodes,
>> where an update would make life better.
>> So, as our OSD-nodes have to care for VM's too, it's not the problem
>> to let them drain so migrate all of them to other nodes.
>> Just reboot? Perhaps not, cause all OSD's will begin to
>> remap/backfill, they are instructed to do so. Well, declare them as
>> "osd lost"?
>> Dangerous. Is there another way I miss in doing node-maintenance?
>> Will we have to wait for bobtail for far less hassle with all
>> remapping and resources?
>
> By default the monitors won't mark an OSD out in the time it takes to
> reboot, but if maintenance takes longer, you can drain data from the
> node.
Hi,

what time is that (in seconds) and how can we reliably test this?

Regards,

--ck

  parent reply	other threads:[~2012-12-03 19:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-03 19:05 Best practice with 0.48.2 to take a node into maintenance Oliver Francke
2012-12-03 19:14 ` Josh Durgin
2012-12-03 19:21   ` Oliver Francke
2012-12-03 19:45     ` Smart Weblications GmbH - Florian Wiessner
2012-12-03 20:13       ` Oliver Francke
2012-12-03 20:22         ` Gregory Farnum
2012-12-03 19:49   ` Christopher Kunz [this message]
2012-12-03 20:39     ` David Clarke
2012-12-03 20:50       ` Smart Weblications GmbH - Florian Wiessner
2012-12-03 20:59         ` David Clarke
2012-12-04 10:35           ` Christopher Kunz
2012-12-04 21:31             ` David Clarke

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=50BD0243.2050109@de-punkt.de \
    --to=chrislist@de-punkt.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 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.