Skip to content

Plan wider object writes in one metadata frame - #535

Merged
matrixarkai merged 1 commit into
mainfrom
star-write-quorum-pipeline
Nov 9, 2026
Merged

matrixarkai merged 1 commit into
mainfrom
star-write-quorum-pipeline

Conversation

@matrixarkai

Copy link
Copy Markdown
Owner

Summary

  • plan the current manifest, placement, and as many as 32 data-group routes in one confirmed metadata frame
  • resolve as many as 32 chunk-group routes per metadata barrier
  • remember older server width limits and use bounded eight- or four-route reads on later operations
  • use the widened confirmed plan for distributed object writes

For a 32-group object, the planning path now uses one metadata exchange instead of a manifest read, a placement read, and four route reads.

Validation

  • cargo check -j1 --all-targets --all-features
  • cargo test -j1 --all-features --test object_writer_connections -- --test-threads=1 (20 passed)
  • cargo test -j1 --all-features --lib thirty_two_routes -- --test-threads=1 (2 passed)
  • full library sweep: 725 passed, 33 ignored; one unrelated timing-sensitive case failed, then both exact matching cases passed on an immediate single-threaded rerun

@matrixarkai
matrixarkai requested a review from bjmeetsfo November 9, 2026 16:50
@matrixarkai
matrixarkai merged commit 48f2ef0 into main Nov 9, 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