Closed GoogleCodeExporter closed 8 years ago
As a workaround, you may want to simply disable the idle timeout,
by setting it to 0 in the redis configuration.
Using the epoll device, Redis is able to support a large number
of connections anyway, so using intermittent connections to
decrease the number of connections is not so useful IMO.
However, you may want to use the idle timeout as a safety
mechanism to close connections associated to broken/stuck
clients. Please note you have an underlying keepalive
mechanism with TCP, supposed to take care of network issues.
So the only situation where a server-side idle timeout is
really useful is with stuck clients (i.e. clients still alive
but frozen). In my experience, this is not so frequent, so
I tend to deactivate idle timeouts on all my database systems.
Regards,
Didier.
Original comment by didier...@gmail.com
on 23 Feb 2011 at 11:22
See also https://github.com/antirez/redis/pull/37
It's a one line fix that I have implemented here:
https://github.com/catwell/redis/commit/97e501a53367bf25e489dbe81ad9fedf5ff9f8ba
Original comment by catwell...@gmail.com
on 23 Feb 2011 at 2:21
Thanks, I've added this together with showing the database number in the prompt
for interactive sessions. You don't want to call FLUSHDB against the wrong
database ;-).
https://github.com/pietern/redis/compare/69bfdc%5E%5E...69bfdc
Original comment by pcnoordh...@gmail.com
on 6 Mar 2011 at 8:13
Issue 504 has been merged into this issue.
Original comment by pcnoordh...@gmail.com
on 1 Apr 2011 at 12:24
Issue 541 has been merged into this issue.
Original comment by pcnoordh...@gmail.com
on 2 May 2011 at 9:15
Original issue reported on code.google.com by
nike.gur...@gmail.com
on 23 Feb 2011 at 10:21