Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-58301

Kubernetes Plugin Repeated Socket Ping Timeout Exceptions

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • kubernetes-plugin
    • 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

            Unassigned Unassigned
            autarchprinceps autarch princeps
            Votes:
            5 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: