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

Several minutes delay at end of job

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      At the end of a build, as this seems to be finished, Jenkins then shows the spinner during many minutes. Note this happens with many (still have to double-check to say all?) our jobs.

      I'm attaching threadDumps of the whole server:

      • two during the issue
      • one after to be able to analyze the difference if necessary

      The slave on which the offending job was running is rhel6-5

      Thanks for any feedback.

        Attachments

          Issue Links

            Activity

            Hide
            jglick Jesse Glick added a comment -

            Possible duplicate.

            Show
            jglick Jesse Glick added a comment - Possible duplicate.
            Hide
            corneil_duplessis Corneil du Plessis added a comment -

            Disabling the disk-usage plugin allowed us to get rid of the huge delay at the end of the job.

            Our workspace has about 80k files.

            I think the plugin is collecting the info from the slave over the network.
            Jobs that run on the master or where the workspace has fewer files doesn't suffer the same delay.
            I don't know enough about the Jenkins Master and Slave interaction to suggest a solution.

            Show
            corneil_duplessis Corneil du Plessis added a comment - Disabling the disk-usage plugin allowed us to get rid of the huge delay at the end of the job. Our workspace has about 80k files. I think the plugin is collecting the info from the slave over the network. Jobs that run on the master or where the workspace has fewer files doesn't suffer the same delay. I don't know enough about the Jenkins Master and Slave interaction to suggest a solution.
            Hide
            batmat Baptiste Mathus added a comment -

            Still to be confirmed, but first analysis led me to JENKINS-21718 (see attached thread dumps, a Disk Usage thread is always present doing a DiskUsageUtil.isSymlink call).

            We just uninstalled disk usage to see if this makes a difference. Waiting to restart Jenkins asap to check.

            Show
            batmat Baptiste Mathus added a comment - Still to be confirmed, but first analysis led me to JENKINS-21718 (see attached thread dumps, a Disk Usage thread is always present doing a DiskUsageUtil.isSymlink call). We just uninstalled disk usage to see if this makes a difference. Waiting to restart Jenkins asap to check.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              batmat Baptiste Mathus
              Votes:
              3 Vote for this issue
              Watchers:
              9 Start watching this issue

                Dates

                Created:
                Updated: