I am using the library node_redis as the client for a micro-service message client that I am writing. Clients get messages from their application in their outbox that they need to send to other services. Everything is working great but I am trying to build some resilience on the part of the application that uses the redis client to municate with the redis-server.

My idea is that the redis client-server connection status should be highly available to the clients. I mean that if a connection goes down, I would like to know within the second instead of the default timeout of 300 seconds. Currently I am using the free redislabs tier hosted on AWS, but I should be moving this to run in its own container on my kubernetes cluster.

I need to know the state of client connections in the network because I would like to not send messages when the network conditions are not right and not rely on the error handling to handle this sort of event. Knowing how often and when these high latency events occur will also help me diagnose and improve my network and my microservices.

Note: I wanted to set the connect_timeout value in the client options but this is listed as deprecated.

I am using the library node_redis as the client for a micro-service message client that I am writing. Clients get messages from their application in their outbox that they need to send to other services. Everything is working great but I am trying to build some resilience on the part of the application that uses the redis client to municate with the redis-server.

My idea is that the redis client-server connection status should be highly available to the clients. I mean that if a connection goes down, I would like to know within the second instead of the default timeout of 300 seconds. Currently I am using the free redislabs tier hosted on AWS, but I should be moving this to run in its own container on my kubernetes cluster.

I need to know the state of client connections in the network because I would like to not send messages when the network conditions are not right and not rely on the error handling to handle this sort of event. Knowing how often and when these high latency events occur will also help me diagnose and improve my network and my microservices.

Note: I wanted to set the connect_timeout value in the client options but this is listed as deprecated.

• javascript
• node.js
• performance
• redis
• node-redis

Share Improve this question Follow asked Nov 12, 2017 at 20:10 tensaitensai 1,69633 gold badges1818 silver badges2323 bronze badges 2

• Couldn't you use the "retry_strategy" option? There is also an event (reconnecting) being fired when the library tries to reconnect to the redis-server. To be fair this event isn't what you're looking for since it is emitted when the library tries to reconnect and not when the connection has been lost but you could use it together with a custom retry strategy. – Siggy Commented Dec 16, 2017 at 1:47
• How did you end up dealing with this? – Ed Spencer Commented Jun 21, 2018 at 13:51

Add a ment  | 

1 Answer 1

Sorted by: Reset to default 3

Something like that?

var redis = require('redis');
var client = redis.createClient();
var reconnectAfter = 15000;

client.on( 'error', function () {
  console.log( (new Date()) + " Redis: disconnect");
  setTimeout( connect, reconnectAfter);
});

connect = function(){
  client = redis.createClient();
}