From: Dan Mick <dan.mick@inktank.com>
To: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: [ceph-commit] HEALTH_WARN 192 pgs degraded
Date: Wed, 24 Oct 2012 20:58:38 -0700 [thread overview]
Message-ID: <5088B8EE.7080109@inktank.com> (raw)
In-Reply-To: <5088824A.4000700@catalyst.net.nz>
>>> HEALTH_WARN 192 pgs degraded; 192 pgs stuck unclean; recovery 21/42
>>> degraded
>>> (50.000%)
>> This is simply because you only have 1 osd but the default policy is 2x
>> replication. As such, all PGs are 'degraded' because they are only
>> replicated once.
>>
>> If you add another OSD to your cluster the warning will go away.
>>
>> sage
>>
>
> The other alternative is to just set the pool(s) replication size to 1,
> if you are just wanting a single osd for (say) testing:
>
> $ ceph osd pool set <your pool(s)> size 1
>
> I find it I need to restart ceph after doing the above, it then sorts
> itself out to a nice healthy status!
OTOH it should be noted that I'm constantly running test clusters with
replication 2, #osd 1, and they're "unhealthy", and work just fine.
(These are test clusters, clearly, but...nothing wrong with them.)
next prev parent reply other threads:[~2012-10-25 3:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5087F3AE.8080601@gmail.com>
2012-10-24 14:55 ` [ceph-commit] HEALTH_WARN 192 pgs degraded Josh Durgin
2012-10-24 15:40 ` Sage Weil
2012-10-25 0:05 ` Mark Kirkwood
2012-10-25 3:58 ` Dan Mick [this message]
[not found] ` <CAJCPpWJy=k2Sw6iRH-wPq85uWCY7yRA3yE6kBUYwfuQsm2Hz7g@mail.gmail.com>
2012-10-25 22:53 ` Mark Kirkwood
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=5088B8EE.7080109@inktank.com \
--to=dan.mick@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=mark.kirkwood@catalyst.net.nz \
/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.