Exit DynamoDB tryToLock when stop channel is closed#6640
Merged
Conversation
If the stop channel is closed (e.g. an error is returned which triggers close(stop) in Lock), this loop will spin and use 100% CPU.
ncabatoff
previously approved these changes
Apr 25, 2019
briankassouf
approved these changes
Apr 30, 2019
briankassouf
pushed a commit
that referenced
this pull request
Jun 4, 2019
* Exit DynamoDB tryToLock when stop channel is closed If the stop channel is closed (e.g. an error is returned which triggers close(stop) in Lock), this loop will spin and use 100% CPU. * Ensure ticker is stopped
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
3 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.
If the stop channel is closed (e.g. an error is returned which triggers
close(stop) in Lock), this loop will spin and use 100% CPU.