From: Martin Mailand <martin@tuxadero.com>
To: Sage Weil <sage@newdream.net>
Cc: ceph-devel@vger.kernel.org
Subject: Re: crushmap errors
Date: Mon, 14 Nov 2011 15:12:59 +0100 [thread overview]
Message-ID: <4EC121EB.10101@tuxadero.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1111111444490.30348@cobra.newdream.net>
Hi Sage,
1. The crushtool grammer fix is working for me. Thanks.
2. I think if an admin puts the extra rack info into the ceph.conf file,
than it should do what expected. I understand your worries but on the
other end ceph is not an end user tool, and people should know what they
do and balance there racks evenly.
Just my two cents.
-martin
Am 11.11.2011 23:51, schrieb Sage Weil:
> On Fri, 11 Nov 2011, Martin Mailand wrote:
>> Hi,
>> I used in ceph v0.38 the host and rack feature in the conf during an mkcephfs.
>> Now I have to problems with the crushmap
>>
>> 1. I cannot compile a ceph genearated crushmap.
>> crushtool -c file.txt -o file
>> file.txt:4 error: parse error at '.0'
>
> Whoops, will push a patch to stable shortly. The grammer wasn't
> recognizing '.' as a legal character.
>
>> 2. Why are 2 racks are not enough for 2 failure domains?
>> From the commit:
>> If there are>2 racks, separate across racks.
>
> Well, technically they are. My worry is that it's more likely that racks
> will have significantly vary capacity (i.e. crush weight) due to, say, 1
> full rack and a second 1/2 rack. If the policy forces replicas be placed
> across racks things won't balance well.
>
> I suppose there should be an argument like --min-racks that controls that
> threshold?
>
> sage
> --
> 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
next prev parent reply other threads:[~2011-11-14 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 22:19 crushmap errors Martin Mailand
2011-11-11 22:51 ` Sage Weil
2011-11-14 14:12 ` Martin Mailand [this message]
2011-11-14 15:45 ` Kelly Kane
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=4EC121EB.10101@tuxadero.com \
--to=martin@tuxadero.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@newdream.net \
/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.