Reusing Redis Connection: Socket Closed Unexpectedly - node-redis

Question

First, let me tell you how I'm using Redis connection in my NodeJS application:

I'm re-using one connection throughout the app using a singleton class.

class RDB {

    static async getClient() {
        if (this.client) {
            return this.client
        }

        let startTime = Date.now();

        this.client = createClient({
            url: config.redis.uri
        });

        await this.client.connect();

        return this.client;
    }

}

For some reason - that I don't know - time to time my application crashes giving an error without any reason - this happens about once or twice a week:

Error: Socket closed unexpectedly

Now, my questions:

Is using Redis connections like this alright? Is there something wrong with my approach?
Why does this happen? Why is my socket closing unexpectedly?
Is there a way to catch this error (using my approach) or any other good practice for implementing Redis connections?

Yash Dixit · Accepted Answer · 2022-06-16 07:49:29Z

13

I solved this using the 'error' listener. Just listening to it - saves the node application from crashing.

client.on("error", function(error) {
   console.error(error);
   // I report it onto a logging service like Sentry. 
});

answered Jun 16, 2022 at 7:49

Yash Dixit

3161 gold badge3 silver badges13 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

chovy Over a year ago

Does the error say why its crashing?

morganney Over a year ago

Probably a timeout from an unused socket.

Herve Mutombo Over a year ago

Does the client reconnect automatically?

Jack Lin · Accepted Answer · 2022-04-21 14:31:09Z

6

I had similar issue of socket close unexpectedly. The issue started while I upgraded node-redis from 3.x to 4.x. The issue was gone after I upgraded my redis-server from 5.x to 6.x.

answered Apr 21, 2022 at 14:31

Jack Lin

1211 bronze badge

Comments

Nimantha · Accepted Answer · 2022-06-25 08:23:40Z

You should declare a private static member 'client' of the RDB class, like this:

private static client;

In a static method, you can't reference instance of 'this', you need to reference the static class member like this:

RDB.client

And it would be better to check, whether the client's connection is open, rather than simply checking if the client exists (considering you are using the 'redis' npm library). Like this:

if (RDB.client && RDB.client.isOpen)

After the changes, your code should look like this:

class RDB {
    private static client;

    static async getClient() {
        if (RDB.client && RDB.client.isOpen) {
            return RDB.client;
        }

        RDB.client = createClient({
            url: config.redis.uri
        });

        await RDB.client.connect();

        return RDB.client;
    }
}

Note: the connect() method and isOpen property only exist in redis version ^4.0.0.

Giangimgs · Accepted Answer · 2024-01-04 10:31:07Z

4

I got the same issue (Socket Closed Unexpectedly) but only with the remote Redis servers, so I figured out that maybe there is a problem with the TLS. So I tried to use redis:// instead of rediss://, and yes it was working stable.

answered Jan 4, 2024 at 10:31

Giangimgs

1,2081 gold badge15 silver badges16 bronze badges

Comments

Janiis · Accepted Answer · 2024-05-13 06:26:32Z

1

There is option pingInterval you can pass to createClient function to keep socket alive. Ping server every 3 seconds.

export const redis = createClient({
    url: 'redis://localhost:6379',
    pingInterval: 3000,
});

answered May 13, 2024 at 6:26

Janiis

1,5961 gold badge14 silver badges22 bronze badges

Comments

Phat Tran · Accepted Answer · 2024-02-02 16:05:11Z

0

I switched to ioredis with the same configuration and this issue is gone.

answered Feb 2, 2024 at 16:05

Phat Tran

3,9901 gold badge23 silver badges26 bronze badges

Collectives™ on Stack Overflow

Reusing Redis Connection: Socket Closed Unexpectedly - node-redis

6 Answers 6

3 Comments

Comments

Comments

Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

6 Answers 6

3 Comments

Comments

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related