Skip to content

DAOS-18544 object: reserved targets for GX object (#17585)#17699

Open
gnailzenh wants to merge 1 commit intorelease/2.6from
liang/rebuild/b2_6_gx_reserved
Open

DAOS-18544 object: reserved targets for GX object (#17585)#17699
gnailzenh wants to merge 1 commit intorelease/2.6from
liang/rebuild/b2_6_gx_reserved

Conversation

@gnailzenh
Copy link
Contributor

The current DAOS only reserves RF × group_size targets for a GX object, whereas it should reserve targets_per_domain × RF.

In addition, when the number of reserved targets is a fixed value, the likelihood of losing those targets grows significantly as the cluster scales, which can cause collocated shards and extra data movement during rebuild.

This patch changes the number of reserved targets for a GX object to be no less than 30% of the targets.

Steps for the author:

  • Commit message follows the guidelines.
  • Appropriate Features or Test-tag pragmas were used.
  • Appropriate Functional Test Stages were run.
  • At least two positive code reviews including at least one code owner from each category referenced in the PR.
  • Testing is complete. If necessary, forced-landing label added and a reason added in a comment.

After all prior steps are complete:

  • Gatekeeper requested (daos-gatekeeper added as a reviewer).

The current DAOS only reserves RF × group_size targets for a GX object,
whereas it should reserve targets_per_domain × RF.

In addition, when the number of reserved targets is a fixed value, the
likelihood of losing those targets grows significantly as the cluster
scales, which can cause collocated shards and extra data movement
during rebuild.

This patch changes the number of reserved targets for a GX object to
be no less than 30% of the targets.

Signed-off-by: Liang Zhen <gnailzenh@gmail.com>
@gnailzenh gnailzenh requested review from a team as code owners March 13, 2026 07:42
@github-actions
Copy link

Errors are Unable to load ticket data
https://daosio.atlassian.net/browse/DAOS-18544

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant