Connection is Closed

ioRedis@4.9.0 Redis Server Version: 5 Using Redis sentinel on production.

Error: Connection is closed. at Redis.sendCommand (/nodeApi/node_modules/ioredis/built/redis.js:552:24)

I have specified the retryStragey, which is working if any redis node(master) goes down and I am assuming it should work for this case too. Or do I need to specify some other option?

var redis = require('ioredis'),
client = Promise.promisifyAll(redis.createClient( {
	sentinels: config.redis.endpoints,
	name: config.redis.masterName,
	prefix: config.database.redisPrefix,
	pass: config.database.redisPassword,
	role:"slave",
	retry_strategy: function (options) {
		if (options.error.code === 'ECONNREFUSED') {
			// End reconnecting on a specific error and flush all commands with a individual error
			return new Error('The server refused the connection');
		}
		if (options.total_retry_time > 1000 * 60 * 60) {
			// End reconnecting after a specific timeout and flush all commands with a individual error
			return new Error('Retry time exhausted');
		}
		if (options.times_connected > 10) {
			// End reconnecting with built in error
			return undefined;
		}
		// reconnect after
		return Math.max(options.attempt * 100, 500);
	}
})),

client.on("error", function (err) {
	console.log("Error " + err);
});

[luin]

Just set retryStrategy to null will do the trick:

const redis = new Redis(redisDsn, {
  retryStrategy: null
});

redis.on('end', () => {
  log.warn('shutting down service due to lost Redis connection');

  lightship.shutdown();
});

[luin]

@gajus Actually it’s documented https://github.com/luin/ioredis#auto-reconnect, but in another format:

retryStrategy is a function that will be called when the connection is lost. The argument times means this is the nth reconnection being made and the return value represents how long (in ms) to wait to reconnect. When the return value isn’t a number, ioredis will stop trying to reconnect, and the connection will be lost forever if the user doesn’t call redis.connect() manually.

So besides retryStrategy: null, you can also write retryStrategy() { return false }. The documentation needs a restructure anyway as it becomes too long to read.