25 Sep
2024
25 Sep
'24
12:29 p.m.
Hi Eugen, I've just torn down and completely respun my cluster, on 17.2.7. Recreated my CRUSH rule, set osd_pool_default_crush_rule to its rule_id, 1. Created a new pool. That new pool still has crush_rule 0, just as before and contrary to what you're seeing. I'm a bit puzzled, because I'm out of ideas as to what could break on my cluster and work fine on yours, to cause this. Odd. Cheers, Florian