Replies: 1 comment
-
I have some trouble following your request. The socket-proxy has no timeout by default, it’s keepalive interval is 1s against the Unix socket. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I thought it would be better to open a new discussion regarding this topic.
In short, I had problems in the past with images that were not managing correctly a connection timeout, below some references:
TSDProxy
Sablier
This 'issue' is in reality the correct behavior of the socket proxy, reference.
Would you consider to add a feature where is possible to disable this connection timeout for specific images through a label added to the service?
What I would consider an ugly solution would be to set a timeout limit of 7days or more and cron a reboot of the images to always establish a new connection to the socket proxy.
On the other hand what might be a more 'nicer' solution might be the capability from the proxy to understand if a label disables completely the connection timeout.
For example, given that TSDProxy was going in panic in such situations (I've no idea if new versions solved the issue), defining the labels something like what follows could be a workaround:
This way the socket proxy recognizes that the timeout should be completely disabled for such service.
On the other hand I've not evaluated possible security/performance implications of disabling the connection timeout.
Beta Was this translation helpful? Give feedback.
All reactions