[JIRA] [github-plugin] (JENKINS-27041) Thousands of threads created by thousands of GitHub pushes

Thu, 19 Feb 2015 13:39:22 -0800

Issue Type: Bug Bug
Assignee: recampbell
Components: github-plugin
Created: 19/Feb/15 9:34 PM
Description:

A Jenkins instance using this plugin was found to have more than 4400 threads with this stack trace:

}}
"Waiting to acquire /scratch/jenkins/workspace/SS-JOB : Computer.threadPoolForRemoting [#37]" daemon prio=10 tid=0x00007f084019e800 nid=0x3229 in Object.wait() [0x00007f083497a000]
    java.lang.Thread.State: WAITING (on object monitor)
       at java.lang.Object.wait(Native Method)
       at java.lang.Object.wait(Object.java:503)
       at hudson.slaves.WorkspaceList.acquire(WorkspaceList.java:245)
       - locked <0x0000000773632e50> (a hudson.slaves.WorkspaceList)
       at hudson.slaves.WorkspaceList.acquire(WorkspaceList.java:224)
       - locked <0x0000000773632e50> (a hudson.slaves.WorkspaceList)
       at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1446)
       at hudson.model.AbstractProject._poll(AbstractProject.java:1425)
       at hudson.model.AbstractProject.poll(AbstractProject.java:1336)
       at com.cloudbees.jenkins.GitHubPushTrigger$1.runPolling(GitHubPushTrigger.java:81)
       at com.cloudbees.jenkins.GitHubPushTrigger$1.run(GitHubPushTrigger.java:106)
       at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
       at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
       at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
       at java.util.concurrent.FutureTask.run(FutureTask.java:262)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
       at java.lang.Thread.run(Thread.java:745)
{{



Looking at the logs, there were 1150 GitHub push notifications for SS-JOB over 12 hours. Each created a polling thread and competed for a lock on the workspace. Each polling request took 1-6 seconds.



Such a high thread count had other knock on effects, such as high CPU usage when counting threads.



So we should figure out a way to either eliminate the duplicate polling or just keep the thread count down.
Environment: 1.580.2
Project: Jenkins
Priority: Major Major
Reporter: recampbell
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.

Reply via email to