Closed calebTomlinson closed 10 years ago
node_redis connection errors, if not handled, are a fatal error for node.js.
A logstash redis went down and took an application with it. This shouldn't be default behavior.
Swallowing the errors is very simple, but perhaps a queue would be a better long term solution.
I would still like to see that messages don't get lost while redis is down, but I'm closing this issue.
node_redis connection errors, if not handled, are a fatal error for node.js.
A logstash redis went down and took an application with it. This shouldn't be default behavior.
Swallowing the errors is very simple, but perhaps a queue would be a better long term solution.