Hi,
For HEALTH_WARN the best thing I found is to change pool size to 1,
it raises "1 pool(s) have no replicas configured" warning almost
instantly and it can be reverted very quickly for empty pool.
any osd flag (noout, nodeep-scrub etc.) cause health warnings. ;-)
But HEALTH_ERR is a bit more tricky. Any ideas?
I think if you set a very low quota for a pool (e.g. 1000 bytes or so)
and fill it up it should create a HEALTH_ERR status, IIRC.
Zitat von George Shuklin <george.shuklin@xxxxxxxxx>:
I have hell of the question: how to make HEALTH_ERR status for a
cluster without consequences?
I'm working on CI tests and I need to check if our reaction to
HEALTH_ERR is good. For this I need to take an empty cluster with an
empty pool and do something. Preferably quick and reversible.
For HEALTH_WARN the best thing I found is to change pool size to 1,
it raises "1 pool(s) have no replicas configured" warning almost
instantly and it can be reverted very quickly for empty pool.
But HEALTH_ERR is a bit more tricky. Any ideas?
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
