From: Daniel Friesen <lists@nadir-seen-fire.com>
To: ceph-devel@vger.kernel.org
Subject: Removing an OSD?
Date: Sun, 13 Feb 2011 09:57:22 -0800 [thread overview]
Message-ID: <4D581B82.4090507@nadir-seen-fire.com> (raw)
I read through most of the documentation on the wiki, though there is
one thing I couldn't find.
The OSD cluster expansion/contraction page lists information on adding a
node, but nothing about removing one.
In particular there are two things I'm curious about.
Firstly, when you want to remove a node (decommissioning the hardware,
etc...) how do you mark it so that ceph will start migrating data away
from it onto other OSDs?
Secondly, how does removing an osd interact with the sequential ids of
OSDs? The importance of that, including not skipping numbers was
underlined strongly on another page.
--
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]
next reply other threads:[~2011-02-13 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 17:57 Daniel Friesen [this message]
2011-02-13 18:32 ` Removing an OSD? Sage Weil
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=4D581B82.4090507@nadir-seen-fire.com \
--to=lists@nadir-seen-fire.com \
--cc=ceph-devel@vger.kernel.org \
--cc=daniel@nadir-seen-fire.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.