Redis cluster connection closed by server error

1,355 views
Skip to first unread message

chilumb...@gmail.com

unread,
Oct 6, 2015, 11:51:40 AM10/6/15
to Redis DB
I have a redis cluster with 6 nodes total; 3 masters each with one slave. All the nodes seem to be working just fine except for one master instance with its slave. For this master and it's slave, overtime i run the "redid-cli monitor" command in the terminal, i get the error:

    Error: Server closed the connection

We are also using predis to access our redis cluster, and it seems that any queries directed to this troublesome master and slave (even with the MOVED TO message), we get the following errors:

    2015-10-04 22:00:09 66513 Error while reading from the Line Server [. tcp: //192.168.2.100: 6379]

It seems like the main cause starts with the redis servers as demonstrated with the error they are producing with the redids-cli monitor command. What can possibly be causing these errors?

I tried creating a new slave from scratch, and tested the redis-cli command and still getting the Server closed the connection error.

 

Josiah Carlson

unread,
Oct 10, 2015, 12:03:52 AM10/10/15
to redi...@googlegroups.com
Are you running in a cloud hosting provider? Have you checked your firewall rules? What other debugging have you performed?

--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+u...@googlegroups.com.
To post to this group, send email to redi...@googlegroups.com.
Visit this group at http://groups.google.com/group/redis-db.
For more options, visit https://groups.google.com/d/optout.

chilumb...@gmail.com

unread,
Nov 8, 2015, 10:44:49 PM11/8/15
to Redis DB
The issue happened to be with running sentinel with the redis cluster. So after i turn off sentinel, this error went away. Apparently, it is pointless (for the purpose of failover) to use senile with the redis cluster as it handles failover on its own
Reply all
Reply to author
Forward
0 new messages