[JENKINS-58065] Making ContainerExecProc periodically send a newline to keep a socket alive #513
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
AFAIU, this timeout is controlled by kubelet
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
JENKINS-58065
The deeper issue is that
BourneShellScriptreturns aProcwhich does not promptly exit (it will not exit until the user process does), which is wasteful given that theProcis discarded (we do not check its stdio nor exit code). I do not believe jenkinsci/durable-task-plugin#92 addresses that. Even if that were fixed, this patch could be useful for slowSynchronousNonBlockingStepExecutions (gigantic Git clone, perhaps).Tested interactively in an AKS cluster.