On May 25, 2026, at 10:16 AM, Adam Prycki <aprycki@man.poznan.pl> wrote:
On 19/05/2026 17:44, Anthony D'Atri wrote:
We initially selected 8+3 over 4+2 because we expect rebuilds to take very long with nodes this big and we don't want to loose redundancy Fair enough. You get more nines with m=3 for sure, though the wider profile itself will mean slower scrubs and recovery. I suspect you set mon_osd_down_out_subtree_limit? We didn't configure that settings before.
I see that by default it is configured at rack level.
What benefit it would have for out deployment?
You can set it so that when an entire host fails, recovery does not automatically begin. The idea is that usually you can get the host back up faster than you can recover then backfill.
I don't quite understand it's description in the documentation.
Trust me, it used to be worse.
Should it be configure to higher level than failure domain of the pool?