which case will trigger read tcp i/o timeout error?

[sttming]

No description provided.

[funny-falcon-at-joomcode]

If server didn't write answer for query for a long time.
Notably, if client issued blocking command which blocks for a long time, it will certainly lead to tcp i/o timeout.

But in the wild some timeouts are really possible: couple of packet loss easely leads to several second pauses. In out setup (aws) we did experienced tcp i/o timeout often (usually once a month, but sometimes two time a week) until I raised IOTimeout up to 4 seconds.

[abhay8nitt]

I too got this @funny-falcon-at-joomcode
"error":"redispipe.io error: {address: myredis.usw2.cache.amazonaws.com:6379}, cause: read tcp 10.x.x.x:10908->10.y.y.y.:6379: use of closed network connection"
should increasing IOTimeout help here in the Opts ?

[funny-falcon-at-joomcode]

I bet you did close connection concurrently. Сб, 13 марта 2021 г. в 01:52, Abhay Mishra ***@***.***>:

…

I too got this @funny-falcon-at-joomcode <https://github.com/funny-falcon-at-joomcode> "error":"redispipe.io error: {address: myredis.usw2.cache.amazonaws.com:6379}, cause: read tcp 10.x.x.x:10908->10.y.y.y.:6379: use of closed network connection" should increasing *IOTimeout* help here in the Opts ? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#13 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH6E6637XVBXI2ZAMR4ZJALTDKEJFANCNFSM4TQR6QCA> .

[sttming]

I find that tcp i/o timeout error always triggered when there is a long time gc pause when I execute pressure test.Should increasing IOTimeout larger than possible max gc pause?