|
||||||||
|
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.
Maybe it depends on how long it takes to remove the node. We're running Docker nodes on some old hardware, so removal might take a bit longer for us. We were experiencing at least one deadlock per day. We're not running that many nodes per minute, but if the ComputerRetentionWork happens to run at the same time as a node is being removed, the deadlock can occur. (I couldn't find where the ComputerRetentionWork was scheduled, so I don't know how often that runs...).
I'm not sure what you mean by escalating the Jenkins.removeNode() code - could the public removeNode() be unsynchronized, obtain a lock on the Queue, then call a private, synchronized removeNode() method?