Skip to content

Spread object copies across available failure domains - #309

Merged
matrixarkai merged 1 commit into
mainfrom
fix/placement-domain-diversity
Oct 28, 2026
Merged

matrixarkai merged 1 commit into
mainfrom
fix/placement-domain-diversity

Conversation

@matrixarkai

Copy link
Copy Markdown
Owner

The root placement planner could select its first two candidates from the same failure domain even when another eligible domain was available. Select one candidate per domain before filling any remaining copies using the existing candidate order. Deployments with fewer domains than copies retain their fallback behavior.

A regression failed on the old planner with two copies selecting a and b from the same rack instead of a and c from distinct racks. It covers one through five copies across three domains, a single-domain deployment, insufficient nodes, and snapshot restoration with exact committed-byte accounting. CI now runs this guard by exact name and the contributor guide updates its guard counts.

Validation: the regression fails on the old planner and passes with the fix. Complete library suites pass: default features 497 passed and 27 ignored; all features 534 passed and 28 ignored. Ten metadata consensus process tests and one coupled metadata/chunk recovery test pass. The locked all-feature/all-target build check passes. Ignored tests and multi-host validation are outside this change.

@matrixarkai
matrixarkai merged commit 80d2d95 into main Oct 28, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants