Fix the task count check in TrafficController #11783
Open
+64
−23
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
Signed-off-by: Jihoon Son <ghoonson@gmail.com>
|
build |
|
build |
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.
A follow-up to #11730. If that is the only task at the moment, the
TrafficControllershould allow the task to process regardless of how much host memory it uses. However, this check was missing in the loop below, which would have all subsequent tasks hung if a task that uses a large memory is submitted while there are some tasks running.This PR fixes this bug. Additionally, it improves the
TrafficControllerto use the condition variable instead of polling as suggested in #11730 (comment). Finally, the terminology inThrottlingExecutorSuitehas been fixed as suggested in #11730 (comment).