From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Josh Durgin <josh.durgin@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: chaning pg_num / pgp_num after adding more osds
Date: Tue, 06 Nov 2012 08:32:15 +0100 [thread overview]
Message-ID: <5098BCFF.6050004@profihost.ag> (raw)
In-Reply-To: <50984F82.3010706@inktank.com>
Am 06.11.2012 00:45, schrieb Josh Durgin:
> On 11/05/2012 06:14 AM, Stefan Priebe - Profihost AG wrote:
>> Hello list,
>>
>> Is there a way to change the number of pg_num / pgp_num after adding
>> more osds?
>
> The pg_num/pgp_num settings are only used by mkcephfs at install time.
>
>> I mean i would like to start with 16 OSDs but i think i'll expand over
>> time to up to 100 OSDs. So i think i need to tune pg_num / pgp_num.
>
> You can specify pg_num when creating a pool:
>
> ceph osd pool create <name> <pgnum>
>
> But you don't want to have too many (thousands per osd). Being able
> to change the number of pgs in a pool (pg splitting/merging) is in
> the works, but in the mean time you can create more pools after you add
> a bunch of osds to keep your pg/osd ratio around 100.
Thanks Josh for your explanation. I'm not sure if i already understood
what pg is at all.
First i see that ceph is creating 832 pgs for 12 osds in my case per
default. This is 69,3333333 per OSD. You're talking about 100 - is the
default calculation broken or hardcoded?
When i have one pool with 800 pgs and i add 20 new OSDs how does a new
pool help? I mean the old pools will stay with 800 pgs.
Thanks again!
Greets,
Stefan
next prev parent reply other threads:[~2012-11-06 7:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 14:14 chaning pg_num / pgp_num after adding more osds Stefan Priebe - Profihost AG
2012-11-05 23:45 ` Josh Durgin
2012-11-06 7:32 ` Stefan Priebe - Profihost AG [this message]
2012-11-06 10:59 ` Sage Weil
2012-11-06 11:07 ` Stefan Kleijkers
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=5098BCFF.6050004@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=josh.durgin@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 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.