Redis Sentinel - ERR max number of clients reached
854 views
Skip to first unread message
ansh_l
unread,
Feb 14, 2016, 2:32:57 PM2/14/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Redis DB
We are using Redis with 1 master and 3 slaves where each node has Sentinel running on it as well. We have been running this configuration for a few years and never had any issues but yesterday I saw an issue with our a Redis cluster we created last week which is running exactly the same configuration. Connecting to Redis sentinel was giving "ERR max number of clients reached" error to the application trying to connect to Sentinel. Here are some details:
I got the same error when I tried connecting to this Sentinel using redis-cli.I could connect but I would get this "ERR max number of clients reached " when I issued any command e.g. info.
Restarting Sentinel Service corrected the issue.
We run the redis-server executable in sentinel mode
The only difference between our old cluster and the new one is that this one is running 2.8.22 vs 2.8.17 on the old one
What's the default maxclient for sentinel; how do you control it? The info command on Sentinel doesn't show number of clients connected.
Has anyone encountered similar issue? What might be causing it?