Assuming that you have a replicated pool with 3 replicas and min_size = 2, I would think
stopping 2 OSD daemons, or 2 OSD containers would guarantee HEALTH_ERR. Similarly, if you
have a replicated pool with 2 replicas, still with min_size = 2, stopping 1 OSD should do
Dominic L. Hilsbos, MBA
Vice President - Information Technology
Perform Air International Inc.
From: mj [mailto:firstname.lastname@example.org]
Sent: Saturday, October 23, 2021 4:06 AM
Subject: [ceph-users] Re: How to make HEALTH_ERR quickly and pain-free
Op 21-01-2021 om 11:57 schreef George Shuklin:
I have hell of the question: how to make HEALTH_ERR
status for a cluster
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.
To get HEALTH_WARN we always simply set something like noout, but we
also wonder if there's a nice way to set HEALTH_ERR, for the same purpose.
ceph-users mailing list -- ceph-users(a)ceph.io
To unsubscribe send an email to ceph-users-leave(a)ceph.io