Disconnects do not return ConnectionError for lazy connections about txredisapi HOT 2 CLOSED

I think docs are misleading about this point. reconnect=True is certainly coded to not raise any errors if no connections are active at the moment and is trying to make reconnects invisible to the end user. ConnectionError are only raised for commands that was sent before connection failure but not received responses until disconnected.

I think if you need response from Redis or failure within guaranteed period of time, you can't rely on ConnectionError anyway. Network connection might stall, server might be turned off, wire might be broken and you won't get any response (including failure) until TCP will drop connection by timeout. It seems to me that the only reliable way to guarantee response time is to do timing out on the client side. Deferred.addTimeout() from Twisted 16.5 can probably help.

from txredisapi.

Thanks! Makes sense.

from txredisapi.