From: Joao Eduardo Luis <joao.luis@inktank.com>
To: Bryant Ng <bryantng@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Crush and Monitor questions
Date: Wed, 12 Dec 2012 17:37:37 +0000 [thread overview]
Message-ID: <50C8C0E1.6060909@inktank.com> (raw)
In-Reply-To: <ka84oo$sa3$1@ger.gmane.org>
Hello Bryant,
On 12/11/2012 08:23 PM, Bryant Ng wrote:
> Hi,
>
> I'm pretty new to Ceph and am just learning about it.
>
> Where are the CRUSH maps stored in Ceph? In the documentation I see you
> use the 'crushtool' to compile and decompile the crush map.
The crushmap is kept alongside with the osdmap, and shared by the monitors.
> I understand that if a single monitor comes online, it can talk to the
> other existing monitors to get the cluster map but how does it work on
> initial startup? Or if the entire Ceph clusters goes down b/c of power
> failure or something.
If you add a new monitor to an existing cluster, it will synchronize
with the existing monitors and will obtain all their infos, including
the crushmap. Updates to the crushmap will also be shared among the
monitors in the quorum.
If you are starting up fresh, you will have to either add your custom
crushmap to the monitors (using the ceph tool), or stick with the
default crushmap (which only defines something along the lines of a
'default' root, a 'defaultrack' rack and a 'localhost' host).
If the entire cluster goes down... well, if the monitors are not up they
won't be able to share the crushmap. When they are brought back up, then
they will pick up where they left. But I'm not sure if I understand what
your question is.
-Joao
next prev parent reply other threads:[~2012-12-12 17:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 20:23 Crush and Monitor questions Bryant Ng
2012-12-12 1:15 ` Bryant Ng
2012-12-12 17:37 ` Joao Eduardo Luis [this message]
2012-12-12 19:02 ` Bryant Ng
2012-12-12 19:32 ` Joao Eduardo Luis
2012-12-13 19:43 ` Bryant Ng
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=50C8C0E1.6060909@inktank.com \
--to=joao.luis@inktank.com \
--cc=bryantng@gmail.com \
--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.