-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
Operative system: 4.14.72-68.55.amzn1.x86_64
JDK:
openjdk version "1.8.0_181"
OpenJDK Runtime Environment (build 1.8.0_181-b13)
OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode)
Jenkins version: Jenkins ver. 2.138.2 running directly
Plugin version: 1.41-SNAPSHOT build on revision d4bdd6b83a7102330fd97ffbbd067edc34e47f97Operative system: 4.14.72-68.55.amzn1.x86_64 JDK: openjdk version "1.8.0_181" OpenJDK Runtime Environment (build 1.8.0_181-b13) OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode) Jenkins version: Jenkins ver. 2.138.2 running directly Plugin version: 1.41-SNAPSHOT build on revision d4bdd6b83a7102330fd97ffbbd067edc34e47f97
We recently upgraded our Jenkins instance to the latest LTS (2.138.2) and started noticing some irregularities with the EC2 plugin, namely:
- A lot more build nodes were created than before, for the same amount of incoming items in the build queue
- This caused an increased amount of AWS API calls, namely StopInstances event. Possibly related to the previous point.
This led us to try out the latest snapshot, 1.41-SNAPSHOT build on revision d4bdd6b83a7102330fd97ffbbd067edc34e47f97. A few hours later, our Jenkins instance had a deadlock problem that is described in the log I'm attaching.
Notice how the Gerrit plugin stops processing events after the EC2 plugin deadlock, this ultimately left our Jenkins unresponsive.
One important bit of information might be that we're using the Stop/Disconnect on Idle Timeout plugin option.
We're happy to provide more information if needed.
- is related to
-
JENKINS-53858 Deadlock on EC2 resources
- Fixed but Unreleased
-
JENKINS-53401 Random FileNotFoundException when creating lots of agents in parallel threads
- Resolved
- relates to
-
JENKINS-55189 Thread deadlock when spinning up hosts with ec2-plugin
- Resolved
-
JENKINS-54298 Jenkins crashes with Deadlock with EC2 Plugin
- Closed