Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
base: master
Are you sure you want to change the base?
DAOS-16702 rebuild: restart rebuild for a massive failure case #15343
Changes from 1 commit
967b84e
a952a14
0a34490
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Question] As @liw mentioned last week, if this ALIVE event means rank state from SUSPECT to ALIVE , and there is a rebuild running, and its rebuild status is not finished, we will abort rebuild unexpected ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know what method can differenciate/avoid that case, even one engine crashed and reboot again in short time, it possibly reflect as SUSPECT+ALIVE.
Seems in SWIM protocol, it is not required to report ALIVE event when remove from SUSPECT status.