[JIRA] [core] (JENKINS-12396) Jobs remain on executor for 20 minutes after they finish

[dan...@beckweb.net (JIRA)]

Daniel Beck commented on JENKINS-12396 Jobs remain on executor for 20 minutes after they finish I don't know if it's because our Jenkins Master is Windows based and NTFS is not good at handling deletes, or that we have a lot of jobs or that our jobs are quite large (many hundreds of files) or some combination of these but this stage can regularly take in excess of an hour to complete after the job has reported that it has finished. The stack trace shows Jenkins is busy with determining what builds may be deleted, not the actual deleting itself. It feels like it would be nicer if the build discard process occurred as a background housekeeping operation rather than as an inline part of the latest build, possibly also only having a single cleanup process rather than every job being able to trigger these tasks concurrently might be a good idea. Needs stronger justification than "it doesn't work on my instance". Get a few more thread dumps for this thread to determine where it's spending the most time. Could well be too little RAM on the Jenkins master to keep builds in memory, resulting in repeated build loading and discarding from memory.

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.