From: Joao Eduardo Luis <joao.luis@inktank.com>
To: Jim Schutt <jaschut@sandia.gov>
Cc: Greg Farnum <greg@inktank.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: OSDMonitor: don't allow creation of pools with > 65535 pgs
Date: Tue, 18 Dec 2012 00:14:59 +0000 [thread overview]
Message-ID: <50CFB583.3070305@inktank.com> (raw)
In-Reply-To: <50CB488E.3090005@sandia.gov>
On 12/14/2012 03:41 PM, Jim Schutt wrote:
> Hi,
>
> I'm looking at commit e3ed28eb2 in the next branch,
> and I have a question.
>
> Shouldn't the limit be pg_num > 65536, because
> PGs are numbered 0 thru pg_num-1?
>
> If not, what am I missing?
>
> FWIW, up through yesterday I've been using the next branch and this:
>
> ceph osd pool set data pg_num 65536 --allow-experimental-feature
> ceph osd pool set metadata pg_num 65536 --allow-experimental-feature
> ceph osd pool set data pgp_num 65536 --allow-experimental-feature
> ceph osd pool set metadata pgp_num 65536 --allow-experimental-feature
>
> using cephfs clients, and have seen no trouble with
> misdirected ops, etc.
>
> -- Jim
>
Jim,
A new patch went into next that increases the default maximum pg_num to
65536, and also adds an option ('mon max pool pg num') that will allow
this value to be adjusted.
-Joao
prev parent reply other threads:[~2012-12-18 0:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 15:41 OSDMonitor: don't allow creation of pools with > 65535 pgs Jim Schutt
2012-12-14 16:59 ` Joao Eduardo Luis
2012-12-14 17:41 ` [EXTERNAL] " Jim Schutt
2012-12-18 0:14 ` Joao Eduardo Luis [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=50CFB583.3070305@inktank.com \
--to=joao.luis@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@inktank.com \
--cc=jaschut@sandia.gov \
/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.