Redis error -connection reset

1,811 views
Skip to first unread message

Vinodh Krishnamoorthy

unread,
Sep 28, 2013, 12:48:09 PM9/28/13
to redi...@googlegroups.com

In our redis logs - I am seeing frequent connection reset by peer's. From the error it looks like flushing to disk takes very long and reset client connections. Any insights/pointers on what should be done? Should I disable snapshotting and aof?

Sep 20 00:27:32 redis-6379[25023]: Error writing to client: Connection reset by peer

Sep 28 05:55:00 redis-6379[20913]: Background saving started by pid 26083

Sep 28 05:55:01 redis-6379[20913]: Error writing to client: Connection reset by peer

Sep 28 05:55:01 redis-6379[20913]: Accepted 10.92.170.239:56362


Sep 28 08:35:18 redis-6379[20913]: Background saving started by pid 28025

Sep 28 08:35:18 redis-6379[20913]: Asynchronous AOF fsync is taking too long (disk is busy?). Writing the AOF buffer without waiting for fsync to complete, this may slow down Redis.

Sep 28 08:35:19 redis-6379[20913]: Error writing to client: Connection reset by peer

Sep 28 08:35:19 redis-6379[20913]: Error writing to client: Connection reset by peer

Sep 28 08:35:19  redis-6379[20913]: Error writing to client: Connection reset by peer


Thanks in advance for any pointers.


-Vinodh

Josiah Carlson

unread,
Oct 2, 2013, 1:59:31 AM10/2/13
to redi...@googlegroups.com
Looking at your logs, the maximum delay due to snapshotting/aof rewriting is about 1 second. It would seem that your clients have short timeouts on their commands, and will disconnect if they need to wait too long. Maybe increase your timeouts on your clients?

 - Josiah


--
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/groups/opt_out.

Reply all
Reply to author
Forward
0 new messages