All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joao Eduardo Luis <joao.luis@inktank.com>
To: YS3fpFE2ykfB@dyweni.com, ceph-devel@vger.kernel.org
Subject: Re: Documentation Discrepancy - Manual Configuration
Date: Wed, 23 Apr 2014 01:23:03 +0100	[thread overview]
Message-ID: <535707E7.3070603@inktank.com> (raw)
In-Reply-To: <6b1a50710afdfd0b10133934be7eac38@pl1.haspere.com>

On 04/18/2014 08:10 AM, Dyweni - Ceph-Devel wrote:
> Hi,
>
> Testing Ceph with 0.79.
>
> 1 Monitor
> 2 OSDs
>
>
> Following the instructions here
> (http://ceph.com/docs/master/install/manual-deployment/)... I arrive at
> this state:
>
> ------
>      cluster e3e1a87b-d282-41b5-b4ad-fb3f969e164f
>       health HEALTH_WARN 192 pgs degraded; 192 pgs stuck unclean
>       monmap e1: 1 mons at {a=10.208.39.100:6789/0}, election epoch 1,
> quorum 0 a
>       osdmap e16: 2 osds: 2 up, 2 in
>        pgmap v21: 192 pgs, 3 pools, 0 bytes data, 0 objects
>              2004 MB used, 59381 MB / 65536 MB avail
>                   192 active+degraded

Indeed, ceph's default pool size is 3.  However, during the manual 
deployment guide you followed, on the "Monitor Bootstrap" section, 14th 
step, you certainly configured ceph.conf.  During this step, the guide 
presents you with an example configuration file containing the option 
'osd pool default size = 2', which overrides the default pool size of 3.

Furthermore, later during the 'Adding OSDs' section, this is made 
obvious right on the first paragraph.

Could this be made more obvious to a new-comer, probably.  But the info 
is there :)

   -Joao

>
> 'ceph osd dump' shows this:
> ------
> ...
> pool 0 'data' replicated size 3 min_size 2 ...
> pool 1 'metadata' replicated size 3 min_size 2 ...
> pool 2 'rbd' replicated size 3 min_size 2 ...
> ...
> ------
>
>
>
> It's not until I add a third OSD, or reduce the size of the pools, does
> the 192 pgs become unstuck and migrate towards active+clean.
>
>
>
> I think the documentation should indicate that three nodes are required
> for Ceph to become optimal.
>
>
>


-- 
Joao Eduardo Luis
Software Engineer | http://inktank.com | http://ceph.com

      reply	other threads:[~2014-04-23  0:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-18  7:10 Documentation Discrepancy - Manual Configuration Dyweni - Ceph-Devel
2014-04-23  0:23 ` 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=535707E7.3070603@inktank.com \
    --to=joao.luis@inktank.com \
    --cc=YS3fpFE2ykfB@dyweni.com \
    --cc=ceph-devel@vger.kernel.org \
    /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.