-
Bug
-
Resolution: Fixed
-
Blocker
-
-
workflow-api 2.31
The graph here in this description more clearly depicts whats going on. I'm the only one using this jenkins server today...
Around 5pm, i kicked off a pipeine. The pipeline builds a container and then uses that container to run some pytests...
It is during that last "postbuild" phase, the CPU runs real hot. While the pytest shards are running, they are just doing a pytest run and then i capture the junit.xml file.
The reason why this is a problem is that with too many of these running at the same time, Jenkins blips out and we cannot contact the web interface because when the CPU is pegged.. it basically crashes the master.
Here are details about my jenkins:
My jenkins is 100% current:
- Jenkins ver. 2.147
- Please note I did today accept the plugin updates described on https://github.com/jenkinsci/jep/blob/master/jep/210/README.adoc#abstract
- relates to
-
-
- Resolved
-
-
JENKINS-38381 [JEP-210] Optimize log handling in Pipeline and Durable Task
-
- Resolved
-
-
JENKINS-56851 Flush durable task output before agent shutdown or before writing lastLocation
-
- Open
-
- links to
[JENKINS-54073] "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Jon B
created issue -
Jon B
made changes -
| Summary | Original: Jenkins Master Host CPU pegs at 50% | New: Jenkins Master Host CPU pegs during parallel jobs |
Jon B
made changes -
| Attachment | New: image-2018-10-14-17-35-11-037.png [ 44776 ] |
Jon B
made changes -
| Description |
Original:
AWS CPU Reports: !image-2018-10-14-14-48-32-774.png! SSH'ed into the Jenkins Master Host. Using nmon, I see: !image-2018-10-14-14-50-10-820.png! Docker stats on the host shows me: !image-2018-10-14-14-50-53-021.png! |
New: !image-2018-10-14-17-35-11-037.png|width=671,height=140! |
Jon B
made changes -
| Description | Original: !image-2018-10-14-17-35-11-037.png|width=671,height=140! |
New:
The graph here in this description more clearly depicts whats going on. I'm the only one using this jenkins server today... you can !image-2018-10-14-17-35-11-037.png|width=657,height=137! |
Jon B
made changes -
| Attachment | New: image-2018-10-14-17-36-52-958.png [ 44777 ] |
Jon B
made changes -
| Description |
Original:
The graph here in this description more clearly depicts whats going on. I'm the only one using this jenkins server today... you can !image-2018-10-14-17-35-11-037.png|width=657,height=137! |
New:
The graph here in this description more clearly depicts whats going on. I'm the only one using this jenkins server today... you can !image-2018-10-14-17-35-11-037.png|width=657,height=137! Around 5pm, i kicked off a pipeine. The pipeline builds a container and then uses that container to run some pytests... !image-2018-10-14-17-36-52-958.png|width=329,height=367! It is during that last "postbuild" phase, the CPU runs real hot. While the pytest shards are running, they are just doing a pytest run and then i capture the junit.xml file. The reason why this is a problem is that with too many of these running at the same time, Jenkins blips out and we cannot contact the web interface because when the CPU is pegged.. it basically crashes the master. Here are details about my jenkins: My jenkins is 100% current: * Jenkins ver. 2.147 * Please note I did today accept the plugin updates described on [https://github.com/jenkinsci/jep/blob/master/jep/210/README.adoc#abstract] |
Jon B
made changes -
| Attachment | Original: image-2018-10-14-14-48-32-774.png [ 44775 ] |
Jon B
made changes -
| Attachment | Original: image-2018-10-14-14-50-10-820.png [ 44774 ] |
Hi. It is not analyzable without Jenkins version and thread CPU usage stats.
You can use tools like jvmtop to retrieve the JVM stats