Skip to content
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

DAOS-16702 rebuild: restart rebuild for a massive failure case #15343

Merged
merged 4 commits into from
Oct 29, 2024

Conversation

liuxuezhao
Copy link
Contributor

In special massive failure case -

  1. some engines down and triggered rebuild.
  2. one engine participated the rebuild, not finished yet, it down again, the #failures exceeds pool RF and will not change pool map.
  3. That engine restarted by administrator.

In that case should recover the rebuild task on the engine, to simplify it now just abort and retry the global rebuild task.
No such issue by the typical recover approach that restart the whole system including the PS leader.

Before requesting gatekeeper:

  • Two review approvals and any prior change requests have been resolved.
  • Testing is complete and all tests passed or there is a reason documented in the PR why it should be force landed and forced-landing tag is set.
  • Features: (or Test-tag*) commit pragma was used or there is a reason documented that there are no appropriate tags for this PR.
  • Commit messages follows the guidelines outlined here.
  • Any tests skipped by the ticket being addressed have been run and passed in the PR.

Gatekeeper:

  • You are the appropriate gatekeeper to be landing the patch.
  • The PR has 2 reviews by people familiar with the code, including appropriate owners.
  • Githooks were used. If not, request that user install them and check copyright dates.
  • Checkpatch issues are resolved. Pay particular attention to ones that will show up on future PRs.
  • All builds have passed. Check non-required builds for any new compiler warnings.
  • Sufficient testing is done. Check feature pragmas and test tags and that tests skipped for the ticket are run and now pass with the changes.
  • If applicable, the PR has addressed any potential version compatibility issues.
  • Check the target branch. If it is master branch, should the PR go to a feature branch? If it is a release branch, does it have merge approval in the JIRA ticket.
  • Extra checks if forced landing is requested
    • Review comments are sufficiently resolved, particularly by prior reviewers that requested changes.
    • No new NLT or valgrind warnings. Check the classic view.
    • Quick-build or Quick-functional is not used.
  • Fix the commit message upon landing. Check the standard here. Edit it to create a single commit. If necessary, ask submitter for a new summary.

Copy link

github-actions bot commented Oct 18, 2024

Ticket title is 'Rebuilding cannot be completed after restarting ranks in cases of massive failures.'
Status is 'In Progress'
https://daosio.atlassian.net/browse/DAOS-16702

@liuxuezhao liuxuezhao marked this pull request as ready for review October 18, 2024 10:55
@liuxuezhao liuxuezhao requested review from a team as code owners October 18, 2024 10:55
@liuxuezhao liuxuezhao removed request for a team October 18, 2024 10:55
@daosbuild1
Copy link
Collaborator

Test stage Functional Hardware Medium Verbs Provider completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-15343/2/execution/node/1397/log

@liuxuezhao liuxuezhao requested a review from liw October 21, 2024 01:03
src/pool/srv_pool.c Outdated Show resolved Hide resolved
src/pool/srv_pool.c Outdated Show resolved Hide resolved
src/pool/srv_pool.c Outdated Show resolved Hide resolved
src/pool/srv_pool.c Outdated Show resolved Hide resolved
liw
liw previously approved these changes Oct 21, 2024
Copy link
Contributor

@wangshilong wangshilong left a comment

Choose a reason for hiding this comment

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

I run test locally, somehow rebuild finished but with 2007 errors, and retry forever.

@liuxuezhao
Copy link
Contributor Author

I run test locally, somehow rebuild finished but with 2007 errors, and retry forever.

at my side I tested DER_STALE will retry and finish. I'll check details with you offline

@wangshilong
Copy link
Contributor

I run test locally, somehow rebuild finished but with 2007 errors, and retry forever.

at my side I tested DER_STALE will retry and finish. I'll check details with you offline

See logs here:

https://build.hpdd.intel.com/job/daos-stack/job/daos/job/PR-15354/1/artifact/Functional%20on%20EL%208.8/control/dmg_pool_query_ranks.py/job.log/*view*/

dmg pool query timeout after restarting rank, but rebuild did not finish too.

@liuxuezhao
Copy link
Contributor Author

https://build.hpdd.intel.com/job/daos-stack/job/daos/job/PR-15354/1/artifact/Functional%20on%20EL%208.8/control/dmg_pool_query_ranks.py/job.log/*view*/

dmg pool query timeout after restarting rank, but rebuild did not finish too.

I ran several test on wolf wit similar steps and be able to reproduce a rebuild timeout issue.
The problem is the ALIVE event got from CRT_EVS_GRPMOD rather than CRT_EVS_SWIM, so cannot ignore CRT_EVS_GRPMOD event.
I changed handle_event a little bit @liw please check if it is good for you.
@wangshilong please retest with the new version. thx

@liuxuezhao liuxuezhao requested review from liw and wangshilong October 23, 2024 01:13
In special massive failure case -
1. some engines down and triggered rebuild.
2. one engine participated the rebuild, not finished yet, it down again,
   the #failures exceeds pool RF and will not change pool map.
3. That engine restarted by administrator.

In that case should recover the rebuild task on the engine, to simplify it now just
abort and retry the global rebuild task.
No such issue by the typical recover approach that restart the whole
system including the PS leader.
Skip-nlt: true

Signed-off-by: Xuezhao Liu <[email protected]>
Skip-nlt: true
Signed-off-by: Xuezhao Liu <[email protected]>
refine handle_event.
Skip-nlt: true

Signed-off-by: Xuezhao Liu <[email protected]>
@liuxuezhao
Copy link
Contributor Author

pushed a new commit to resolve a race condition of rpt not stoped intime when restart new rebuild.

Copy link
Contributor

@wangshilong wangshilong left a comment

Choose a reason for hiding this comment

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

Thanks for fix.

@liuxuezhao liuxuezhao requested review from a team and gnailzenh October 25, 2024 08:11
@gnailzenh gnailzenh merged commit 50128bd into master Oct 29, 2024
53 of 54 checks passed
@gnailzenh gnailzenh deleted the lxz/massive_rb branch October 29, 2024 15:30
jolivier23 pushed a commit that referenced this pull request Dec 11, 2024
* DAOS-16702 rebuild: restart rebuild for a massive failure case

In special massive failure case -
1. some engines down and triggered rebuild.
2. one engine participated the rebuild, not finished yet, it down again,
   the #failures exceeds pool RF and will not change pool map.
3. That engine restarted by administrator.

In that case should recover the rebuild task on the engine, to simplify it now just
abort and retry the global rebuild task.
No such issue by the typical recover approach that restart the whole
system including the PS leader.

Signed-off-by: Xuezhao Liu <[email protected]>
jolivier23 pushed a commit that referenced this pull request Dec 11, 2024
* DAOS-16702 rebuild: restart rebuild for a massive failure case

In special massive failure case -
1. some engines down and triggered rebuild.
2. one engine participated the rebuild, not finished yet, it down again,
   the #failures exceeds pool RF and will not change pool map.
3. That engine restarted by administrator.

In that case should recover the rebuild task on the engine, to simplify it now just
abort and retry the global rebuild task.
No such issue by the typical recover approach that restart the whole
system including the PS leader.

Signed-off-by: Xuezhao Liu <[email protected]>
@mjmac mjmac mentioned this pull request Dec 12, 2024
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.

5 participants