add keepalive for TCP socket in KubePodProcess #10528
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
@subodh and I noticed that the TCP connections to the source stay open in the case this OC issue. It is possible that the ochestrator is not properly detecting that the client on the other side has closed. Adding this keep alive would detect this.
It is not clear why this is happening only in the case of user.
https://stackoverflow.com/questions/1480236/does-a-tcp-socket-connection-have-a-keep-alive