Tokio: no way to set read/write timeout for tokio's TcpStream

[Matrix-Zhang]

especially, the tokio's listener accpeted a new TcpStream, this stream can't configure

[carllerche]

AFAIK, read / write timeouts are a synchronous socket concept.

[Matrix-Zhang]

but when use tokio-codec, the server will keep a lots of half-open tcp streams for a long time(have keepalive), if the client not shutdown the stream, just shutdown the modem...

[carllerche]

To close a socket, you drop the codec (which transitively drops the TcpStream).

[CryptosWolfOfAllStreets]

Close the socket

[Matrix-Zhang]

of cause i know i could actively close the socket, i just want the tcp/ip stack automatic to find the half open connections faster

[sfackler]

You can use the tokio-io-timeout crate to manage read/write timeouts: https://crates.io/crates/tokio-io-timeout

[Matrix-Zhang]

tokio-io-timeout crate fix my issue

[ICEYSELF]

It's 2020 now and async/await have been made stable, and I had same problem. Though timeout is a concept for synchronous socket, it's still convenient to use this in asynchronous world sometime. I found this issue through searching engine.

The crate tokio-io-timeout did not work for me (perhaps due to changes of scheduler). However, tokio::time::timeout exactly met my requirement. I'm to write down this here, and hope this helps other people having the same problem.

[Darksonn]

When using async/await you have the ability to kill any operation whatsoever, which is what tokio::time::timeout allows you to do. Of course, it can also wrap any other asynchronous operation, and will work on those other operations just as fine as it does for TCP streams.