Skip to content

DAOS-17589 pool: not changing fseq for exclude during drain #16418

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

wangdi1
Copy link
Contributor

@wangdi1 wangdi1 commented May 20, 2025

If the target is being drained, then exclude should not change its fseq number, otherwise it may get wrong object layout and interfere the drain process.

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

If the target is being drained, then exclude should not change
its fseq number, otherwise it may get wrong object layout and
interfere the drain process.

Signed-off-by: Di Wang <[email protected]>
@wangdi1 wangdi1 requested review from a team as code owners May 20, 2025 16:44
Copy link

Ticket title is 'exclude should not change the fseq number during drain'
Status is 'Open'
https://daosio.atlassian.net/browse/DAOS-17589

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.

3 participants