Question posted in
The official documentation can be found here.

Redis Error "max number of clients reached"

I am running a nodeJS application using forever npm module.
Node application also connects to Redis DB for cache check. Quite often the API stops working with the following error on the forever log. 

{ ReplyError: Ready check failed: ERR max number of clients reached
    at parseError (/home/myapp/core/node_modules/redis/node_modules/redis-parser/lib/parser.js:193:12)
    at parseType (/home/myapp/core/node_modules/redis/node_modules/redis-parser/lib/parser.js:303:14)
    at JavascriptRedisParser.execute (/home/myapp/ecore/node_modules/redis/node_modules/redis-parser/lib/parser.js:563:20) command: 'INFO', code: 'ERR' }

when I execute the client list command on the redis server it shows too many open connections. I have also set the timeout = 3600 in my Redis configuration.
I do not have any unclosed Redis connection object on my application code.
This happens once or twice in a week depending on the application load, as a stop gap solution I am restarting the node server( it works ).

What could be the permanent solution in this case?

Tags:

2

Answers


  1. Chosen as BEST ANSWER
    0

    I have figured out why. This has nothing to do with Redis. Increasing the OS file descriptor limit was just a temporary solution. I was using Redis in a web application and the connection was created for every new request.

    When the server was restarted occasionally, all the held-up connections by the express server were released.

    I solved this by creating a global connection object and re-using the same. The new connection is created only when necessary.

    You could do so by creating a global connection object, make a connection once, and make sure it is connected before every time you use that. Check if there is an already coded solution depending on your programming language. In my case it was perl with dancer framework and I used a module called Dancer2::Plugin::Redis

    redis_plugin

    Returns a Dancer2::Plugin::Redis instance. You can use redis_plugin to pass the plugin instance to 3rd party modules (backend api) so you can access the existing Redis connection there. You will need to access the actual methods of the the plugin instance.

    In case if you are not running a web-server and you are running a worker process or any background job process, you could do this simple helper function to re-use the connection.
    perl example

    sub get_redis_connection {
    my $redis = Redis->new(server  => "www.example.com:6372" , debug => 0);
    $redis->auth('abcdefghijklmnop');
    return $redis;
}

...

## when required
unless($redisclient->ping) {
      warn "creating new redis connection";
      $redisclient = get_redis_connection();
}

  2. 0

    I was running into this issue in my chat app because I was creating a new Redis instance each time something connected rather than just creating it once.

    // THE WRONG WAY
export const getRedisPubSub = () => new RedisPubSub({
    subscriber: new Redis(REDIS_CONNECTION_CONFIG),
    publisher: new Redis(REDIS_CONNECTION_CONFIG),
});

    and where I wanted to use the connection I was calling

    // THE WRONG WAY
getNewRedisPubsub();

    I fixed it by just creating the connection once when my app loaded.

    export const redisPubSub = new RedisPubSub({
    subscriber: new Redis(REDIS_CONNECTION_CONFIG),
    publisher: new Redis(REDIS_CONNECTION_CONFIG),
});

    and then I passed the one-time initialized redisPubSub object to my createServer function.

    It was this article here that helped me see my error: https://docs.upstash.com/troubleshooting/max_concurrent_connections

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search