pump: getSafeGCTSOForDrainers should be usable after Close #617
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
When we call `Close` on the server, it first calls `cancel` to stop all related background jobs. If we reuse `s.ctx` in `getSafeGCTSOForDrainers` after `Close`, nothing useful can be done.
|
/run-all-tests |
|
LGTM |
|
/run-integration-tests |
|
LGTM |
WangXiangUSTC
approved these changes
May 23, 2019
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.
What problem does this PR solve?
When we call
Closeon the server, it first callscancelto stop all related background jobs. If we reuse
s.ctxingetSafeGCTSOForDrainersafterClose, nothing useful can be done.What is changed and how it works?
Make
ctxa parameter, so that when callinggetSafeGCTSOForDrainersafter
Closewe can pass in a different context.Check List
Tests
Code changes
Side effects
Related changes