Hi, you could check if this is caused by the mina/ssh problems in gerrit: See e.g. https://groups.google.com/forum/#!searchin/repo-discuss/open$20connections/repo-discuss/O1Beo9wRPjc/UziifXyZCAAJ It could be that the plugin just loops on trying to re-open a lost connection.
Björn Am Donnerstag, 30. Juni 2016 19:55:38 UTC+2 schrieb Will Saxon: > > Hello, > > We are consistently seeing very high CPU usage on our Jenkins master > (1.651.1) related to the Gerrit trigger. We are running Jenkins on Linux > (Ubuntu 14.04) using the included Jetty container. > > We're not sure what specifically is causing this, but frequently the > Jenkins process will spike to consume 100% of all 4 CPUs we have allocated > to Jenkins. When pointing jvisualvm or jstack at the Jenkins process during > these events, we see that all of the Gerrit Worker EventThreads are > running; sampling cpu use shows the bulk of the run time is spent in > com.sonymobile.tools.gerrit.gerritevents.GerritHandler.notifyListener(), > with other com.sonymobile.* contributing in various ways. > > When Jenkins is seeing this high CPU usage, patchsets we expect to trigger > jobs do not trigger jobs. In one case yesterday, I knew I needed to > manually trigger (via query and trigger gerrit patches on the main Jenkins > page) 6 patchsets; doing this did not actually cause the associated jobs to > trigger for almost 45 minutes. > > I sent a similar post in May asking about guidelines for setting up the > number of threads associated with this plugin. We're really just looking > for some information on how this plugin is working for other people with > similar configurations to ours (single master, multiple build agents, many > builds triggered/day). We've allocated 4CPU/8GB to the jenkins master and > aside from a couple of very lightweight nightly jobs, we don't run anything > on the master. Whenever we have sustained high CPU usage, it seems entirely > restricted to the Gerrit trigger plugin. It's very disruptive for us and > our development teams often complain that their builds are not triggering. > Is this normal? > > Thanks, > > -Will > -- 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/0c4a233c-7c9f-4fc4-9050-955ec865ceaf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
