DAOS-17142 rebuild: exit rebuild_tgt_status_check_ult when RPT stale #15994
+63
−8
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Ticket title is 'clean up rebuild_tgt_status_check() ULTs for globally-done rebuilds whose leader to target engine IV updates failed' |
liuxuezhao
force-pushed
the
lxz/tgt_check_ult
branch
2 times, most recently
from
be51151 to
7a78480
Compare
rebuild_tgt_status_check_ult() ULT only can exit when rebuild abort or globally done. When rebuild done, the leader notifies each target server by IV LAZY SYNC, the notification lost due to some network issue and lead to dangling rebuild_tgt_status_check_ult. Signed-off-by: Xuezhao Liu <[email protected]>
18 tasks
liuxuezhao
force-pushed
the
lxz/tgt_check_ult
branch
from
7a78480 to
3fcef6b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
rebuild_tgt_status_check_ult() ULT only can exit when rebuild abort or globally done. When rebuild done, the leader notifies each target server by IV LAZY SYNC, the notification lost due to some network issue and lead to dangling rebuild_tgt_status_check_ult.
Steps for the author:
After all prior steps are complete: