-
Bug
-
Resolution: Incomplete
-
Critical
-
None
-
LTS 1.580.1
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.
- is related to
-
JENKINS-39231 WinSW: Automatically terminate runaway processes in Windows services
-
- Resolved
-
[JENKINS-26020] Will not start builds even though there are available slots on executor
Workflow | Original: JNJira [ 160008 ] | New: JNJira + In-Review [ 180215 ] |
Link |
New:
This issue is related to |
Resolution | New: Incomplete [ 4 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |