Re: Inactive PGs should trigger a HEALTH_ERR state

2015-07-22 Thread Sage Weil
On Wed, 22 Jul 2015, Wido den Hollander wrote:
> Hi,
> 
> I was just testing with a cluster on VMs and I noticed that
> undersized+degraded+peering PGs do not trigger a HEALTH_ERR state. Why
> is that?
> 
> In my opinion any PG which is not active+? should trigger a HEALTH_ERR
> state since I/O is blocking at that point.
> 
> Is that a sane thing to do or am I missing something?

IIRC they trigger a WARN state until they are 'stuck' inactive, at which 
point they trigger an ERR state.  The idea is that it is totally normal 
for PGs to be in an inactive state for short periods due to normal cluster 
churn--it's only problematic if they get stuck there.

sage
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Inactive PGs should trigger a HEALTH_ERR state

2015-07-22 Thread Wido den Hollander
Hi,

I was just testing with a cluster on VMs and I noticed that
undersized+degraded+peering PGs do not trigger a HEALTH_ERR state. Why
is that?

In my opinion any PG which is not active+? should trigger a HEALTH_ERR
state since I/O is blocking at that point.

Is that a sane thing to do or am I missing something?

-- 
Wido den Hollander
42on B.V.
Ceph trainer and consultant

Phone: +31 (0)20 700 9902
Skype: contact42on
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html