RepoMirrors/ceph
1
0
Fork 0
mirror of https://github.com/ceph/ceph synced 2025-01-03 01:22:53 +00:00
Code Issues Packages Projects Releases Wiki Activity

doc: describe 'stuck' states we check for

Browse Source 
Signed-off-by: Sage Weil <sage@newdream.net>
This commit is contained in:
Sage Weil 2012-03-06 15:31:29 -08:00
parent d72b821741
commit 2bec51a21e
1 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
doc/ops/manage/failures/osd.rst
View File

@ -56,6 +56,23 @@ daemons will allow the cluster to recover that PG (and, presumably,
many others).
Stuck PGs
=========
It is normal for PGs to enter states like "degraded" or "peering"
following a failure. Normally these states indicate the normal
progression through the failure recovery process. However, is a PG
stays in one of these states for a long time this may be an indication
of a larger problem. For this reason, the monitor will warn when PGs
get "stuck" in a non-optimal state. Specifically, we check for:
* ``inactive`` - the PG is has not ``active`` for too long (i.e., hasn't
been able to service read/write requests)
* ``unclean`` - the PG has not been ``clean`` for too long (i.e.,
hasn't been able to completely recover from a previous failure
* ``stale`` - the PG status hasn't been updated by a ``ceph-osd``,
indicating that all nodes storing this PG may be down
PG down (peering failure)
=========================