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.
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.