From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
To: Sage Weil <sage@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Osd placement rule questions
Date: Thu, 05 Jul 2012 16:55:05 +1200 [thread overview]
Message-ID: <4FF51E29.3000205@catalyst.net.nz> (raw)
In-Reply-To: <Pine.LNX.4.64.1207042055350.6931@cobra.newdream.net>
On 05/07/12 15:57, Sage Weil wrote:
> On Thu, 5 Jul 2012, Mark Kirkwood wrote:
>
>> 2/ Also I would like to be able to say make my number of copies 3, but if I
>> lose datacenter0 (where 2 copies are), don't try to have 3 copies at
>> datacenter1 (so run degraded in that case). Is that possible?
> That is what you get now. Doing the opposite (2 copies in DC1, 1 in DC2,
> but if DC2 is down 3 in DC1) is not currently possible with the crush
> rules.
>
Ah, right - excellent and thanks for clarifying! I guess I was
unconsciously (and incorrectly) thinking that the crush rule would be
modified when (say) datacenter0 was not available.
Cheers
Mark
prev parent reply other threads:[~2012-07-05 4:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 3:45 Osd placement rule questions Mark Kirkwood
2012-07-05 3:57 ` Sage Weil
2012-07-05 4:55 ` Mark Kirkwood [this message]
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=4FF51E29.3000205@catalyst.net.nz \
--to=mark.kirkwood@catalyst.net.nz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox