Unify redis client and handle redis errors #9
Labels
Comments
rahulreddy
added a commit
that referenced
this issue
Aug 17, 2016
Fix #9 This commit offers a cleanup to use unify the redis client usage and add an error handler to handle redis connection errors. The option for offline queue has been removed (for now) as it may grow the callback queue to infinity and eventually result in a RangeError.
rahulreddy
added a commit
that referenced
this issue
Aug 17, 2016
Fix #9 This commit offers a cleanup to unify the redis client usage and add an error handler to handle redis connection errors. The option for offline queue has been removed (for now) as it may grow the callback queue to infinity and eventually result in a RangeError.
Merged
rahulreddy
added a commit
that referenced
this issue
Aug 17, 2016
Fix #9 This commit offers a cleanup to unify the redis client usage and add an error handler to handle redis connection errors. The option for offline queue has been removed (for now) as it may grow the callback queue to infinity and eventually result in a RangeError.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
UtapiClient currently does not listen to the redis error event, which may flood the logs when Redis
server is unavailable.
This also calls for unification of the redis client as we want the configuration to be setup in one place for easier maintenance.
Lastly, we want to remove the offline queue option, since there is no limit on the callback queue, it may grow to infinity resulting in a
RangeError. This option can be re-introduced later after this PR on ioredis is merged, which gives the developer an option to manage the offline queueredis/ioredis#241
The text was updated successfully, but these errors were encountered: