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.
HDDS-15412. [DataNode] Disk volume-specific container replication thread pool #10595
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
base: master
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
HDDS-15412. [DataNode] Disk volume-specific container replication thread pool #10595
Changes from all commits
b4d6eed1dd7771b4e2d4f0385c584ec8bcee90008aFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
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.
This volume selection has a reservation side effect: chooseNextVolume() increments the target volume's committed bytes. Doing it here makes the reservation lifetime hard to pair with execution.
If the task is later dropped before DownloadAndImportReplicator runs, the reservation is leaked. Conversely, if a pull attempt hits REPLICATION_LIMIT_REACHED, DownloadAndImportReplicator releases the reservation, marks the same task QUEUED, and the retry reuses task.getVolume() without reserving again, so committed bytes can be decremented repeatedly.
Can we move volume selection/reservation into each actual pull attempt, or explicitly track whether the task currently owns a reservation?
Uh oh!
There was an error while loading. Please reload this page.