All of lore.kernel.org
 help / color / mirror / Atom feed
From: Smart Weblications GmbH - Florian Wiessner <f.wiessner@smart-weblications.de>
To: ceph-devel <ceph-devel@vger.kernel.org>
Cc: Oliver Francke <Oliver.Francke@filoo.de>, josh.durgin@inktank.com
Subject: Re: Best practice with 0.48.2 to take a node into maintenance
Date: Mon, 03 Dec 2012 20:45:18 +0100	[thread overview]
Message-ID: <50BD014E.90304@smart-weblications.de> (raw)
In-Reply-To: <EB4A37AF-6A19-4F66-B5E3-AED15BECED06@filoo.de>

Am 03.12.2012 20:21, schrieb Oliver Francke:
> Hi Josh,
> 
> Am 03.12.2012 um 20:14 schrieb Josh Durgin <josh.durgin@inktank.com>:
> 
>> 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.
>>
>> A simple way to rate limit it yourself is by slowly lowering the
>> weights of the OSDs on the host you want to update, e.g. by 0.1 at a
>> time and waiting for recovery to complete before lowering again. Once
>> they're at 0 and the cluster is healthy, they're not responsible for
>> any data anymore, and the node can be rebooted.
>>
> 
> true. Should have mentioned knowing smooth way. But for a planned reboot this take way too much time ;)
> But if it's recommended, it's recommended ;)
> 


I did rolling reboots of our whole cluster a few days ago (3.4.20). When the
system reboots and no fsck is done, ceph won't start to backfill in my setup.

I had some nodes do fsck after upgrade so ceph marked the osd as down and
started to backfill, but once the missing osd was back up running again, the
backfill stopped and ceph did just a little bit of peering and was healthy in a
few minutes again (2-5 minutes)...




-- 

Mit freundlichen Grüßen,

Florian Wiessner

Smart Weblications GmbH
Martinsberger Str. 1
D-95119 Naila

fon.: +49 9282 9638 200
fax.: +49 9282 9638 205
24/7: +49 900 144 000 00 - 0,99 EUR/Min*
http://www.smart-weblications.de

--
Sitz der Gesellschaft: Naila
Geschäftsführer: Florian Wiessner
HRB-Nr.: HRB 3840 Amtsgericht Hof
*aus dem dt. Festnetz, ggf. abweichende Preise aus dem Mobilfunknetz
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-12-03 19:51 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 [this message]
2012-12-03 20:13       ` Oliver Francke
2012-12-03 20:22         ` Gregory Farnum
2012-12-03 19:49   ` Christopher Kunz
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=50BD014E.90304@smart-weblications.de \
    --to=f.wiessner@smart-weblications.de \
    --cc=Oliver.Francke@filoo.de \
    --cc=ceph-devel@vger.kernel.org \
    --cc=josh.durgin@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.