Skip to content

DAOS-18825 pool: include excluded ranks as DOWNOUT at creation time - #18994

Open
wangshilong wants to merge 1 commit into
release/2.8from
shilongw/DAOS-18825-2.8
Open

DAOS-18825 pool: include excluded ranks as DOWNOUT at creation time#18994
wangshilong wants to merge 1 commit into
release/2.8from
shilongw/DAOS-18825-2.8

Conversation

@wangshilong

Copy link
Copy Markdown
Contributor

DAOS placement uses consistent hashing to distribute data across nodes and fault domains. In theory, each node/domain should have the same probability of being selected for data placement, which helps ensure balanced data distribution.

However, pool create currently filters out excluded ranks and only creates VOS pools on alive ranks. If a node has only one alive rank, this can cause data imbalance. To address this, pool create now sends DOWNOUT ranks to the PS leader. VOS pools are still created only on alive ranks, but DOWNOUT ranks are included in the pool map. During layout calculation, placement remaps data from DOWNOUT ranks onto alive ranks, reducing imbalance. After reintegration, data can be moved back to the reintegrated ranks.

Features: rebuild pool

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).

@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown

Ticket title is 'Imbalanced object distribution for G32 oclass in pool with asymmetric fault domain topology'
Status is 'In Review'
https://daosio.atlassian.net/browse/DAOS-18825

@wangshilong
wangshilong force-pushed the shilongw/DAOS-18825-2.8 branch from 8a2e6c6 to 4987873 Compare September 3, 2026 08:47
DAOS placement uses consistent hashing to distribute data across nodes and
fault domains. In theory, each node/domain should have the same probability
of being selected for data placement, which helps ensure balanced data distribution.

However, pool create currently filters out excluded ranks and only creates VOS pools
on alive ranks. If a node has only one alive rank, this can cause data imbalance.
To address this, pool create now sends DOWNOUT ranks to the PS leader.
VOS pools are still created only on alive ranks, but DOWNOUT ranks are included in
the pool map. During layout calculation, placement remaps data from DOWNOUT ranks
onto alive ranks, reducing imbalance. After reintegration, data can be moved back
to the reintegrated ranks.

Features: rebuild pool
Signed-off-by: Wang Shilong <shilong.wang@hpe.com>
Signed-off-by: Xuezhao Liu <xuezhao.liu@hpe.com>
Co-authored-by: Xuezhao Liu <xuezhao.liu@hpe.com>
@wangshilong
wangshilong force-pushed the shilongw/DAOS-18825-2.8 branch from 4987873 to 049287e Compare September 7, 2026 02:20
@wangshilong
wangshilong marked this pull request as ready for review September 7, 2026 02:31
@wangshilong
wangshilong requested review from a team as code owners September 7, 2026 02:31
@wangshilong wangshilong added release-2.8.1 Targeted for release 2.8.1 priority Ticket has high priority (automatically managed) unclean-cherry-pick Indicates that a cherry-pick had merge conflicts that needed resolving. labels Sep 7, 2026
@daosbuild3

Copy link
Copy Markdown
Collaborator

Test stage Functional Hardware Medium MD on SSD completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-18994/3/execution/node/1672/log

@daosbuild3

Copy link
Copy Markdown
Collaborator

Test stage Functional Hardware Medium MD on SSD completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-18994/4/execution/node/610/log

@daltonbohning daltonbohning left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ftest changes LGTM (they match what is in master)

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

Labels

priority Ticket has high priority (automatically managed) release-2.8.1 Targeted for release 2.8.1 unclean-cherry-pick Indicates that a cherry-pick had merge conflicts that needed resolving.

Development

Successfully merging this pull request may close these issues.

6 participants