Chris Lu bea1357d38 ec: skip physically near-full disks when placing EC shards (#10167) ...

EC placement scored destinations purely by free EC shard slots (derived from
maxVolumeCount) and shard counts, blind to real disk fullness — the same defect
as volume balancing. A disk that is physically full but still shows free EC slots
kept being chosen, and EC shard bytes are captured by statfs free space yet not
by any slot accounting, so the slot math is exactly the metric that can't see EC
fullness.

Treat a disk at/above 90% physical usage as having zero free EC slots at
snapshot-build time, so every existing freeSlots>0 placement predicate excludes
it. Applied in all three snapshot builders (shell countFreeShardSlots, the shared
ecbalancer FromActiveTopology, and the worker ec_balance buildBalancerTopology)
via the shared balancer.DiskTooFullAfter gate. Servers not reporting disk bytes
fall back to slot-only behavior. ec.rebuild recovery is left ungated so shard
recovery can still complete onto fuller disks.

2026-06-30 20:01:55 -07:00

..

balancer_test.go

refactor(ec_balance): make the balance planner per-volume ratio-capable (#9960)

2026-06-14 11:33:31 -07:00

balancer.go

refactor(ec_balance): make the balance planner per-volume ratio-capable (#9960)

2026-06-14 11:33:31 -07:00

place_test.go

ec placement: spread EC shards evenly across machines, not onto the lowest-id one (#9855)

2026-06-07 20:45:17 -07:00

place.go

ec placement: spread EC shards evenly across machines, not onto the lowest-id one (#9855)

2026-06-07 20:45:17 -07:00

shard_ratio.go

refactor(ec_balance): make the balance planner per-volume ratio-capable (#9960)

2026-06-14 11:33:31 -07:00

snapshot_test.go

ec: skip physically near-full disks when placing EC shards (#10167)

2026-06-30 20:01:55 -07:00

snapshot.go

ec: skip physically near-full disks when placing EC shards (#10167)

2026-06-30 20:01:55 -07:00