CEPH filesystem development
 help / color / mirror / Atom feed
From: "Jens Rehpöhler" <jens.rehpoehler@filoo.de>
To: Samuel Just <sam.just@dreamhost.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: ceph -w output
Date: Wed, 04 Jan 2012 12:51:08 +0100	[thread overview]
Message-ID: <4F043D2C.9090306@filoo.de> (raw)
In-Reply-To: <4EEB2813.6060109@filoo.de>

[-- Attachment #1: Type: text/plain, Size: 2458 bytes --]

Hi Sam,

just to inform you: after upgrade to the lastest master (ceph version
0.39-210-gdf84594 (commit:df84594f205bb37d3b062b5b3b9cfd224e6c57d2)

the pgs in "creating" state disappeared. The bugfix seems to work.

Thx again

Jens

Am 16.12.2011 12:14, schrieb Jens Rehpöhler:
> Hi Sam,
>
> thanks for the answers.
>
> We began with osd3 und osd4 for internal reasons. osd1 to 3 will be
> addes in near future.
>
> I will wait until the patch is in the stables branch.
>
> Thanks again
>
> Jens
>
>
> Am 15.12.2011 18:35, schrieb Samuel Just:
>> Sorry for the delay.  It looks like you hit a corner case in our crush
>> implementation.  The short version is that this bug got fixed last
>> week in commit 14f8f00e579083db542568a60cd23d50055c92a3.
>>
>> The long version is that you have osd.3 and osd.4, but not osd.0,
>> osd.1, or osd.2.  The pgs stuck in creating are the ones mapped
>> specifically to osds 0, 1, and 2.  A pg ending in p# (like pg1.0p0) is
>> supposed to map to osd.0 if possible.  With the above patch, those pgs
>> should remap to available osds.
>>
>> -Sam
>>
>> On Thu, Dec 15, 2011 at 1:45 AM, Jens Rehpöhler
>> <jens.rehpoehler@filoo.de> wrote:
>>> Am 14.12.2011 17:43, schrieb Tommi Virtanen:
>>>> On Wed, Dec 14, 2011 at 00:36, Jens Rehpöhler <jens.rehpoehler@filoo.de> wrote:
>>>>> Attached you will find the output you asked for. Is there any limitation
>>>>> on the amount of pools ? We create
>>>>> pools for every customer and store their VM images in that pools. So we
>>>>> will create a lot of pools over time.
>>>> Each pool gets its own set of PGs (Placement Groups). An OSD that
>>>> manages too many PGs will use a lot of RAM. What is "too many" is
>>>> debatable, and really up to benchmarks, but considering we recommend
>>>> about 100 PGs/OSD as a starting point, you probably don't want to go
>>>> two orders of magnitude above that.
>>> Ok .... that will serve our needs. Remains only the "creating" question.
>>>
>>> Any answers to that ?
>>>
>>> Thanks a lot !
>>>
>>> Jens
>>>


-- 
mit freundlichen Grüssen

Jens Rehpöhler

----------------------------------------------------------------------
Filoo GmbH
Moltkestr. 25a
33330 Gütersloh
HRB4355 AG Gütersloh

Geschäftsführer: S.Grewing | J.Rehpöhler | C.Kunz
Telefon: +49 5241 8673012 | Mobil: +49 151 54645798
Hotline: 07000-3378658 (14 Ct/min) Fax: +49 5241 8673020



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

      reply	other threads:[~2012-01-04 11:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-12 19:23 ceph -w output Jens Rehpoehler
2011-12-13 17:57 ` Samuel Just
2011-12-14  8:36   ` Jens Rehpöhler
2011-12-14 16:43     ` Tommi Virtanen
2011-12-15  9:45       ` Jens Rehpöhler
2011-12-15 17:35         ` Samuel Just
2011-12-16 11:14           ` Jens Rehpöhler
2012-01-04 11:51             ` Jens Rehpöhler [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=4F043D2C.9090306@filoo.de \
    --to=jens.rehpoehler@filoo.de \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sam.just@dreamhost.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox