runner: close rate limiter on Stop #635
Merged
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.
redis client is never closed, even after graceful shutdown via Stop(). It is possible to observe this by creating a runner, and calling Stop(), and stopping the redis server. Runner is expected to be stopped, and all components closed, however still logs can be seen that redis is unavailable.
this patch allows runner to actually gracefully close rate limit implementations, so all components are closed gracefully on Stop.