![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Attachments:
|
ThreadDump - After doing disconnect and connect.log, ThreadDump - No jobs can be schedule on node.log |
|
Components:
|
core |
|
Created:
|
11/Dec/14 3:45 PM
|
|
Description:
|
Sometimes our nodes won't be able to start new builds even though there are free slots available.
A workaround for the slaves is to disconnect/connect the slave and it will start to schedule builds again.
I have observed that when this happens for a slave the slave has fewer threads ongoing than an idle slave.
Attaching thread dumps when this happens and after doing an disconnect/connect.
We have seen this issue both on Windows(jlnp) slaves and linux(ssh) slaves as well as on the master node which is running linux.
|
|
Environment:
|
LTS 1.580.1
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Critical]() Critical
|
|
Reporter:
|
Christian Bremer
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/d/optout.
