[JIRA] [core] (JENKINS-32689) Load statistics graph don't show the correct number of executors

[roland.asmann@gmail.com (JIRA)]

Roland Asmann created an issue

Jenkins / JENKINS-32689 Load statistics graph don't show the correct number of executors Issue Type: Bug Assignee: Unassigned Attachments: Jenkins Load 1.png, Jenkins Load 2.png Components: core Created: 29/Jan/16 7:51 PM Environment: Master: Ubuntu14 Slaves: Ubuntu12 / Windows Priority: Minor Reporter: Roland Asmann I just set up a new Jenkins and was checking out how the load was during our nightly builds, when I noticed that the graph is missing 2 executors. Playing with shutting down the slaves it appears to be the executors on the master that are not included in the graph. I am showing the graph for the whole installation, not for any specific node. I must say that checking the graph for the master only actually does show 2 executors! Please check the attached screenshots. On the screenshot with the running project, you can actually see the graph is going down – this also made me Jenkins is not calculating the master executors. Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[chris.4lexander@gmail.com (JIRA)]

Christopher Alexander updated an issue

Jenkins / JENKINS-32689 Load statistics graph don't show the correct number of executors

Change By: Christopher Alexander

I just set up a new Jenkins and was checking out how the load was during our nightly builds, when I noticed that the graph is missing 2 executors. Playing with shutting down the slaves it appears to be the executors on the master that are not included in the graph.

I am showing the graph for the whole installation, not for any specific node. I must say that checking the graph for the master only actually *does* show 2 executors! Please check the attached screenshots. On the screenshot with the running project, you can actually see the graph is going down -- this also made me  think that  Jenkins is not calculating the master executors.

Add Comment

[kboz@java.net (JIRA)]

kboz updated an issue

Jenkins / JENKINS-32689 Load statistics graph don't show the correct number of executors

Change By: kboz Attachment: Load Statistics - master.png

Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[kboz@java.net (JIRA)]

kboz updated an issue

Jenkins / JENKINS-32689 Load statistics graph don't show the correct number of executors

Change By: kboz Attachment: Load Statistics - Jenkins.png

Add Comment

[kboz@java.net (JIRA)]

kboz commented on JENKINS-32689

Re: Load statistics graph don't show the correct number of executors We have a single (master) Windows Jenkins node with 4 executors, no slaves. Running Jenkins v2.48 Viewing the load statistics for the entire system (http://jenkins/load-statistics ) only displays queue length, with zero executors (online, busy or available) Viewing the load statistics just for the master node (http://jenkins/computer/(master)/load-statistics ) displays the executors, but zero queue length.

Add Comment

[kboz@java.net (JIRA)]

kboz edited a comment on JENKINS-32689

Re: Load statistics graph don't show the correct number of executors

We have a single (master) Windows Jenkins node with 4 executors, no slaves. Running Jenkins v2.48

Viewing the load statistics for the entire system ([http://jenkins/load-statistics|http://jenkins/load-statistics)] ) only displays queue length, with zero executors (online, busy or available) !Load Statistics - Jenkins.png! Viewing the load statistics just for the master node ([http://jenkins/computer/(master)/load-statistics|http://jenkins/computer/(master)/load-statistics)] ) over the same period, displays the executors, but zero queue length. !Load Statistics - master.png! Surely these two graphs should look the same, and both include all 4 metrics?

Add Comment

[amedee.vangasse@itextpdf.com (JIRA)]

Amedee Van Gasse commented on JENKINS-32689

Re: Load statistics graph don't show the correct number of executors

This bug also affects me. Jenkins 2.176.3

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)