[JIRA] (JENKINS-53532) Kubernetes java.net.SocketTimeoutException: timeout

[jenkins-ci@carlossanchez.eu (JIRA)]

Carlos Sanchez updated an issue

Jenkins / JENKINS-53532 Kubernetes java.net.SocketTimeoutException: timeout Change By: Carlos Sanchez Summary: KubernetesClientException Kubernetes java.net.SocketTimeoutException : Operation: [get]  for kind: [Pod]  with name: [maven-3-jdk-8-hgdv3]  in namespace: [jenkins]  failed timeout Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[jenkins-ci@carlossanchez.eu (JIRA)]

[jenkins-ci@carlossanchez.eu (JIRA)]

Carlos Sanchez commented on JENKINS-53532

Re: Kubernetes java.net.SocketTimeoutException: timeout If you want to be able to set the pingTimeout in the Jenkins config it needs to be added the same way the connectTimeout and readTimeout I'm closing this issue, as the correct solution is to increase the connectTimeout and readTimeout and in the next release they will be correctly saved. Feel free to open other issue if you want to add pingTimeout

Add Comment

[jenkins-ci@carlossanchez.eu (JIRA)]

Carlos Sanchez resolved as Fixed

Jenkins / JENKINS-53532 Kubernetes java.net.SocketTimeoutException: timeout

Change By: Carlos Sanchez Status: Open Resolved Resolution: Fixed

Add Comment

[xzaphroditemo@gmail.com (JIRA)]

mu qiao updated an issue

Jenkins / JENKINS-53532 Kubernetes java.net.SocketTimeoutException: timeout

Change By: mu qiao Attachment: image-2019-05-22-20-33-26-157.png

Add Comment

[xzaphroditemo@gmail.com (JIRA)]

mu qiao commented on JENKINS-53532

Re: Kubernetes java.net.SocketTimeoutException: timeout As Matthew Ludlum (thx a lot, you save my days) said, adding -Dkubernetes.websocket.ping.interval=<number> fix the ping timeout issue More information is: this so-called 'interval' option changes ping/pong timeout and uses millisecond as unit. I set it to 30 and got log below

Add Comment

[elhayefrat@gmail.com (JIRA)]

elhay efrat commented on JENKINS-53532

Re: Kubernetes java.net.SocketTimeoutException: timeout Matthew Ludlum, there is not a configuration that we can change in the plugin itself, we really need to restart Jenkins for it?

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[aburdajewicz@cloudbees.com (JIRA)]

Allan BURDAJEWICZ commented on JENKINS-53532

Re: Kubernetes java.net.SocketTimeoutException: timeout The original issue java.net.SocketTimeoutException: timeout is due to a Socket Read Timeout. The value can be changed in the kubernetes cloud configuration since version 1.14.9. Before this version, there was a persistent issue and the value was reset to 0 every time the configuration was saved from the UI. Note that until version 1.22.3 a value of 0 does not mean no timeout. If a value of 0 is provided, the fabric8 kubernetes client does not explicitly set a timeout. But the okhttp client defaults to 10s. *A value of 0 actually means 10s*. Since version 1.22.3 of the kubernetes plugin: the minimum value for Read Timeout is 15s the minimum value of the connection timeout is 5s. **** The SocketTimeoutException: sent ping but didn't receive pong within XXXXms is related to the Socket Ping Timeout interval and should be fixed since version 1.19.3 of the kubernetes plugin: https://issues.jenkins-ci.org/browse/JENKINS-58301.

Add Comment