Socket closed unexpectedly

[diegothucao]

Hi mates,
Redis often throw error like above Socket closed unexpectedly, could we turn socket connection off from redis?
Thanks,
Thu

[leibale]

Hi, does your redis server seats behind some kind of a proxy/load balancer? Can you please share some more details on your redis/node configuration?

[diegothucao]

I tried both ways

{
url: setting.ADDRESS_REDIS_URL,
}

And I tried some other way

{
socket: {
port: setting.ADDRESS_REDIS_PORT,
host: setting.ADDRESS_REDIS_HOST,
noDelay: false,
keepAlive: -1,
connectTimeout: 0
},
url: setting.ADDRESS_REDIS_URL,
}

The save/ get value is working but it throw socket issue a lot in logs

Thanks

[guy-microsoft]

Same issue here - it happens in my NodeJS application every 10 minutes, and reconnecting successfully shortly after it.

[leibale]

@diegothucao @guy-microsoft do you use some kind of a proxy/load balancer?

[diegothucao]

no, we do not have it
could we turn socket connect off from redis, for example I just use redis to save and get key, I want to off socket connection.
In previous version, seems it works stablly

[leibale]

What do you mean by "turn socket connect off from redis"?

[diegothucao]

because we are facing issue of socket connection closes, could we do not use socket feature from redis, just normally save and get key... Like we have option like that

[chayim]

@diegothucao Are you saying that you're using a direct connect socket - and that's failing (i.e a unix socket), or that when connecting via a tcp username and host socket things are failing? Can you please bit a bit more explicit?

[phanvanluan94]

I got the same issue.

[diegothucao]

@chayim

{
url: setting.ADDRESS_REDIS_URL,
}

connect like above so it opens say socket close unexpected

[anshul-kai]

I have a multi-server, multi-process application and I'm using redis all over the place. The only instances of redis clients that throw this error are where I'm connecting to the same redis server while using worker threads ie. Connection exists in the main thread and worker thread and the error is constantly thrown every minute. Not an issue when using version 3.

[leibale]

@a-koka can you please share the code that reproduces the error?

[anshul-kai]

@leibale here's a stripped-down version of my code. Hope it's reproducible.

'use strict';

const { Worker, isMainThread } = require('worker_threads');

if (isMainThread) {
  new Worker(__filename);

  require('../common/redis-client').getSubClient().then(redisSubClient => {
    redisSubClient.subscribe('another-channel', data => {
      // do something
    });
  });
} else {
  require('../common/redis-client').getSubClient().then(redisSubClient => {
    redisSubClient.subscribe('channel', data => {
      // do something
    });
  });
}

redis-client.js

'use strict';

const redis = require('redis');

const { REDIS_HOST, REDIS_MAIN_PORT } = process.env;

async function _createClient(port, index) {
  let client;

  client = redis.createClient({ socket: { host: REDIS_HOST, port } });
    await client.connect();

  client.on('error', function(err) {
    console.error('Redis Error:' + err);
  });

  return client;
}

// Each subscribe requires a dedicated redis client.
module.exports.getSubClient = async index => {
  const subClient = await _createClient(REDIS_MAIN_PORT, index);
  return subClient;
};

[brianzable]

This is affecting our application too, very similar client code.