Hi Yehuda,
With regards to the health status of the cluster, it isn't
healthy but I haven't found any way of fixing the placement
group errors. Looking at the ceph health detail it's also
showing blocked requests too?
HEALTH_WARN 1 pgs down; 3 pgs incomplete; 3 pgs stuck inactive;
3 pgs stuck unclean; 7 requests are blocked > 32 sec; 3 osds
have slow requests; pool cloudstack has too few pgs; pool
.rgw.buckets has too few pgs
pg 14.0 is stuck inactive since forever, current state
incomplete, last acting [5,0]
pg 14.2 is stuck inactive since forever, current state
incomplete, last acting [0,5]
pg 14.6 is stuck inactive since forever, current state
down+incomplete, last acting [4,2]
pg 14.0 is stuck unclean since forever, current state
incomplete, last acting [5,0]
pg 14.2 is stuck unclean since forever, current state
incomplete, last acting [0,5]
pg 14.6 is stuck unclean since forever, current state
down+incomplete, last acting [4,2]
pg 14.0 is incomplete, acting [5,0]
pg 14.2 is incomplete, acting [0,5]
pg 14.6 is down+incomplete, acting [4,2]
3 ops are blocked > 8388.61 sec
3 ops are blocked > 4194.3 sec
1 ops are blocked > 2097.15 sec
1 ops are blocked > 8388.61 sec on osd.0
1 ops are blocked > 4194.3 sec on osd.0
2 ops are blocked > 8388.61 sec on osd.4
2 ops are blocked > 4194.3 sec on osd.5
1 ops are blocked > 2097.15 sec on osd.5
3 osds have slow requests
pool cloudstack objects per pg (37316) is more than 27.1587
times cluster average (1374)
pool .rgw.buckets objects per pg (76219) is more than 55.4723
times cluster average (1374)
Ignore the cloudstack pool, I was using cloudstack but not
anymore, it's an inactive pool.
On 22/01/14 16:38, Graeme Lambert wrote: