From: Xiaopong Tran <xiaopong.tran@gmail.com>
To: Sage Weil <sage@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Very unbalanced storage
Date: Sat, 01 Sep 2012 10:52:14 +0800 [thread overview]
Message-ID: <5041785E.3040707@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1208310904570.1531@cobra.newdream.net>
On 09/01/2012 12:05 AM, Sage Weil wrote:
> On Fri, 31 Aug 2012, Xiaopong Tran wrote:
>> Hi,
>>
>> Ceph storage on each disk in the cluster is very unbalanced. On each
>> node, the data seems to go to one or two disks, while other disks
>> are almost empty.
>>
>> I can't find anything wrong from the crush map, it's just the
>> default for now. Attached is the crush map.
>
> This is usually a problem with the pg_num for the pool you are using. Can
> you include the output from 'ceph osd dump | grep ^pool'? By default,
> pools get 8 pgs, which will distribute poorly.
>
> sage
>
>
Here is the pool I'm interested in:
pool 9 'yunio2' rep size 3 crush_ruleset 0 object_hash rjenkins pg_num 8
pgp_num 8 last_change 216 owner 0
So, ok, by default, the pg_num is really small. That's a very dumb
mistake I made. Is there any easy way to change this?
I looked at the tunables, if I upgrade to v0.48.1 or v0.49,
then would I be able to tune the pg_num value?
Thanks for any help, this is quite a serious issue.
Xiaopong
next prev parent reply other threads:[~2012-09-01 2:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 11:11 Very unbalanced storage Xiaopong Tran
2012-08-31 15:00 ` Andrew Thompson
2012-08-31 16:10 ` Sage Weil
2012-08-31 16:24 ` Andrew Thompson
2012-08-31 16:39 ` Gregory Farnum
2012-09-01 2:33 ` Xiaopong Tran
2012-09-01 3:07 ` Sage Weil
2012-08-31 16:43 ` Sage Weil
2012-08-31 16:05 ` Sage Weil
2012-09-01 2:52 ` Xiaopong Tran [this message]
2012-09-01 3:05 ` Sage Weil
2012-09-01 3:15 ` Xiaopong Tran
2012-09-01 6:58 ` Andrew Thompson
2012-09-04 15:59 ` Tommi Virtanen
2012-09-04 16:19 ` Andrew Thompson
2012-09-04 16:43 ` Sage Weil
2012-09-04 16:48 ` Tommi Virtanen
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=5041785E.3040707@gmail.com \
--to=xiaopong.tran@gmail.com \
--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 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.