-
Bug
-
Resolution: Unresolved
-
Major
-
Jenkins version: 2.182
Kubernetes Plugin: 1.16.2
Kubernetes: v1.13.7-eks-c57ff8
I often get issues like this:
java.net.SocketTimeoutException: sent ping but didn't receive pong within 1000ms (after 330 successful ping/pongs)
One single issue breaks the entire task and makes it hard to even cancel the task. Should this not be retried rather than break execution? Our Jenkins will run longer running tasks as well. Any single task breaking stop in the middle is a real issue, and I don't see why one network issue after 330 successful ones (in this case) is such a big issue.
x
- relates to
-
-
- Resolved
-
- links to
[JENKINS-58301] Kubernetes Plugin Repeated Socket Ping Timeout Exceptions
| Environment |
Original:
Jenkins version: 2.182 Kubernetes Plugin: 1.6.2 Kubernetes: v1.13.7-eks-c57ff8 |
New:
Jenkins version: 2.182 Kubernetes Plugin: 1.16.2 Kubernetes: v1.13.7-eks-c57ff8 |
| Link |
New:
This issue relates to |
| Remote Link | New: This issue links to "CloudBees-internal issue (Web Link)" [ 23217 ] |
| Labels | Original: kubernetes kubernetes-plugin plugin timeout | New: timeout |
| Assignee | Original: Carlos Sanchez [ csanchez ] |
Lee McClintock
made changes -
| Description |
Original:
I often get issues like this: java.net.SocketTimeoutException: sent ping but didn't receive pong within 1000ms (after 330 successful ping/pongs) One single issue breaks the entire task and makes it hard to even cancel the task. Should this not be retried rather than break execution? Our Jenkins will run longer running tasks as well. Any single task breaking stop in the middle is a real issue, and I don't see why one network issue after 330 successful ones (in this case) is such a big issue. I set the timeout (both Connection and Read) in the settings of the Kubernetes Plugin as well, but it still only has a timeout of one second. |
New:
I often get issues like this: java.net.SocketTimeoutException: sent ping but didn't receive pong within 1000ms (after 330 successful ping/pongs) One single issue breaks the entire task and makes it hard to even cancel the task. Should this not be retried rather than break execution? Our Jenkins will run longer running tasks as well. Any single task breaking stop in the middle is a real issue, and I don't see why one network issue after 330 successful ones (in this case) is such a big issue. x |