Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Read/Write and connection timeout #111

Open
jakelandis opened this issue Mar 2, 2018 · 0 comments
Open

Read/Write and connection timeout #111

jakelandis opened this issue Mar 2, 2018 · 0 comments

Comments

@jakelandis
Copy link
Contributor

jakelandis commented Mar 2, 2018

If a connection (while in client mode) can not be made we should provide a configurable timeout value (For example /proc/sys/net/ipv4/tcp_syn_retries) .

If the connection on the other end of the connection dies without any warning we should provide configurable read/write timeouts. ( For example SO_RCVTIMEO / SO_SNDTIMEO or poll with timeout if working directly with the socket)

Today, the timeouts are dictated by the OS, which are global can be difficult to change in a manner that does not impact other services on the OS. In particular the general default timeouts for read/write on most OS is very long.

We should leverage the client/language specific features to enable these timeouts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant