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

Jenkins master and slave takes 4 minutes to reconnect

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: remoting
    • Labels:
      None
    • Environment:
      Jenkins master 2.150.3, org.jenkins-ci.main:remoting:3.27 using jnlp to start agent on Windows slave
    • Similar Issues:

      Description

      Whenever we have a connection issue, the slave will try to re-connect to the master but the master is rejecting the connection because the master thinks the connection is already established and at the same time, the master is trying to ping the slave. It takes 4 minutes for the master to figure out the slave was no longer responding before it will clean up and accept the new connection from the slave. I have attached the logs from the master and similar logs from the slave.

      Ideally if the master is failing to ping the slave and there is a new connection request from the slave, it should probably be best to clean up and accept the new connection as early as possible, instead of waiting for the ping timeout.

        Attachments

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              jthompson Jeff Thompson
              Reporter:
              awong29 Alfred Wong
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: