From: Wido den Hollander <wido@widodh.nl>
To: "Sébastien Han" <han.sebastien@gmail.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: osd_pool_default_size
Date: Fri, 26 Oct 2012 15:41:04 +0200 [thread overview]
Message-ID: <508A92F0.7040007@widodh.nl> (raw)
In-Reply-To: <CAOLwVUkvCQm-_UF=OsykCfw+CH7CPxBaXZrwDtH19M-T5EPrgg@mail.gmail.com>
On 10/26/2012 10:17 AM, Sébastien Han wrote:
> Hi Cephers!
>
> Some question about this parameter:
>
> - Why does this parameter need to be in the [mon] section to work?
It's the monitor who is preparing the new pool before creating it. I had
a discussion regarding this with Greg some time ago, can't re-call if
this was on IRC or the ml though.
It however contradicts what's in the docs:
http://ceph.com/docs/master/config-cluster/osd-config-ref/
The docs seem to be wrong at this point:
* src/mon/OSDMonitor.cc *
int OSDMonitor::prepare_new_pool(string& name, uint64_t auid, int
crush_rule,
unsigned pg_num, unsigned pgp_num)
{
..
..
pending_inc.new_pools[pool].size = g_conf->osd_pool_default_size;
..
..
}
This is done by the monitor.
There seems to be some reference for this in src/osd/OSDMap.cc, but that
seems to be for initializing the cluster since it creates the data,
metadata and rbd pool there.
This was fixed in this commit:
https://github.com/ceph/ceph/commit/1292436b8f88ce203bdba97278ce368b1dfa025f
Seems to be because of this message on the ml last year:
http://comments.gmane.org/gmane.comp.file-systems.ceph.devel/2983
So yes, it is odd that something prefixed with "osd" should go into the
mon section.
Wido
> - In my ceph.conf I set a default size of 3:
>
> # rados mkpool lol
> successfully created pool lol
>
> # ceph osd dump | grep lol
> pool 31 'lol' rep size 3 crush_ruleset 0 object_hash rjenkins pg_num 8
> pgp_num 8 last_change 430 owner 18446744073709551615
>
> Now if I retrieve the admin daemon I get,
>
> # ceph --admin-daemon /var/run/ceph/ceph-osd.0.asok config show | grep
> 'osd_pool_default_size'
> osd_pool_default_size = 2
>
> Why? Did I something wrong?
>
> Thanks :)
>
> Cheers!
> --
> 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
>
--
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:[~2012-10-26 13:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 8:17 osd_pool_default_size Sébastien Han
2012-10-26 13:41 ` Wido den Hollander [this message]
2012-10-26 14:32 ` osd_pool_default_size Sébastien Han
2012-10-26 16:18 ` osd_pool_default_size Sage Weil
2012-10-27 23:24 ` osd_pool_default_size Sébastien Han
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=508A92F0.7040007@widodh.nl \
--to=wido@widodh.nl \
--cc=ceph-devel@vger.kernel.org \
--cc=han.sebastien@gmail.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.