-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Draft: Use TCP KEEPALIVE to force closing socket with offline remotes. #4761
base: master
Are you sure you want to change the base?
Conversation
OK. Let's talk about this lazy implementation. On Linux, after ::accept(), TCP_KEEPALIVE is not set by default. Regarding the values, the default TCP ones are far too huge (> 2h).
Note:
|
There are options for this, pretty sure zyre should just set them accordingly, rather than hardcoding? |
Agreed, and I spent quite some time trying to find something less hard-coded,but I did not find anything. For instance, when the socket is created internally by a ZYRE node, the application has no possibility to access it. If you have a pointer, I'll see what I can do with it. |
ZMQ_TCP_KEEPALIVE |
Not sure to understand what you have in mind. I you use What I can do is to use constants for 10, 10 and 120, right, but I still have to |
I mean that zyre or any other application should just use those options if they want to modify this behaviour |
Agreed. It's being a long time I worked on this but I'm pretty sure that even the ZACTOR has no view on the |
I am pretty sure you can get the zmq socket in all of those cases, and then it's just a matter of setting those options |
If this way exists, I lost on this Hide & Seek :-) |
Close issue #4729.