Repository navigation
DAOS-19616 rebuild: only restart for old-map DTXs at migration boundary - #19216
Merged
Merged
Conversation
Restarting rebuild for every non-ready DTX below the stable epoch livelocks rebuild under continuous I/O: each restart samples a new stable epoch, and in-flight writes waiting for async commit always sit just below it. A DTX prepared with the rebuild (or newer) pool map version was sent with a layout that already includes the in-rebuilding target, so it is safe to keep it invisible to migration. Only restart for DTXs from an older map version, which DTX resync should have resolved. Signed-off-by: Mohamad Chaarawi <mohamad.chaarawi@hpe.com>
|
Ticket title is 'FIO crc mismatch detected on 4x node IB config while running HSN cable pulls test' |
github-actions
Bot
added
the
priority
gnailzenh
marked this pull request as ready for review
October 8, 2026 03:31
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Restarting rebuild for every non-ready DTX below the stable epoch livelocks rebuild under continuous I/O: each restart samples a new stable epoch, and in-flight writes waiting for async commit always sit just below it.
A DTX prepared with the rebuild (or newer) pool map version was sent with a layout that already includes the in-rebuilding target, so it is safe to keep it invisible to migration. Only restart for DTXs from an older map version, which DTX resync should have resolved.
Steps for the author:
After all prior steps are complete: