I would bet your java process is running into excess Garbage Collection, causing the entire thing to hang. It probably isn't because of the pipeline itself. Check your garbage collection when this happens to see if you are hung with full collections.
On Tuesday, September 19, 2017 at 6:18:33 PM UTC-6, Chris Packham wrote: > > Hi, > > We've got a setup with a mix of Pipeline, Multi-configuration and > Freestyle jobs. We have a Jenkins master and many slave nodes for > executing the builds. > > Most of the time the pipeline jobs move onto one of the slave nodes > (chosen by the agent label) but occasionally we see issues where one > of the Pipeline jobs gets stuck on the master and causes the web > interface and scheduler to become unresponsive. If we can still access > the web interface we can't abort the stuck job. > > Does this sound familiar to anyone? > > Any suggestions on how to debug this? > > Are my expectations correct that the pipelines initially start on the > master and move to a slave once they hit the agent directive? > > Thanks, > Chris > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b91f0c02-2966-49c1-be38-9a8629ca1887%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
