Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-56773

High master CPU usage introduced by Blue Ocean 1.14.0

    Details

    • Type: Bug
    • Status: Reopened (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: blueocean-plugin
    • Labels:
      None
    • Environment:
      BlueOcean 1.14.0
      Jenkins 1.168
    • Similar Issues:
    • Released As:
      1.15.0

      Description

      We went from BO 1.13.2 to BO 1.14.0.
      After the upgrade, we have seen a major CPU increase on our Jenkins master, leading to really slow UI and job execution, with threads being locked - see screenshot.

      Our master is configured to not run any job ("only build jobs with label expression matching this node").
      Using Jenkins monitor, we saw that ~90% of the CPU time was consumed by calls to the rest endpoint /blue/rest/organizations/jenkins/computers - see screenshot.

      Looking at the release notes from 1.14.0, it seems that JENKINS-52825 has introduced that endpoint and should be an area to investigate.

      We had to rollback BO to 1.13.2 which does not exhibit that behavior.

        Attachments

          Issue Links

            Activity

            Hide
            halkeye Gavin Mogan added a comment -

            disable the executor plugin, its no longer required

            Show
            halkeye Gavin Mogan added a comment - disable the executor plugin, its no longer required
            Hide
            danielbeck Daniel Beck added a comment -

            Removing a plugin from the aggregator/meta plugin doesn't remove the broken functionality from any instances that have it installed.

            Like ci.jenkins.io which got shit for the last several weeks for its recent stability problems. Imagine my surprise seeing dozens of threads hanging in the endpoint mentioned in this issue, and how this issue has been resolved.

            At the very least, admins that generally take care of their instance need to be informed about this with an admin monitor.

            Show
            danielbeck Daniel Beck added a comment - Removing a plugin from the aggregator/meta plugin doesn't remove the broken functionality from any instances that have it installed. Like ci.jenkins.io which got shit for the last several weeks for its recent stability problems. Imagine my surprise seeing dozens of threads hanging in the endpoint mentioned in this issue, and how this issue has been resolved. At the very least, admins that generally take care of their instance need to be informed about this with an admin monitor.
            Hide
            markewaite Mark Waite added a comment -

            As far as I can tell, https://github.com/jenkinsci/blueocean-plugin/releases/tag/blueocean-parent-1.21.0 includes this change. Thanks Jesse Glick for that pull request! I think this can be marked 'Closed' in release blue ocean 1.21.0 with a code fix to prevent the issue.

            Can one of the users that encountered this problem confirm that it is now resolved?

            Show
            markewaite Mark Waite added a comment - As far as I can tell, https://github.com/jenkinsci/blueocean-plugin/releases/tag/blueocean-parent-1.21.0 includes this change. Thanks Jesse Glick for that pull request! I think this can be marked 'Closed' in release blue ocean 1.21.0 with a code fix to prevent the issue. Can one of the users that encountered this problem confirm that it is now resolved?
            Hide
            mwos Michał Woś added a comment - - edited

            We use Blue Ocean and Blue Ocean Executor Info plugins in version 1.22.0 and still have a problem with 

            ```

            /blue/rest/organizations/jenkins/computers/

            ```

            endpoint. It is called very often and hangs for ~5sec each time. Not sure why informations about all executors is needed in the first place when opened blue ocean for a given job and a run. Those informations do not seem to be utilised anywhere in the view.

            Show
            mwos Michał Woś added a comment - - edited We use Blue Ocean and Blue Ocean Executor Info plugins in version 1.22.0 and still have a problem with  ``` /blue/rest/organizations/jenkins/computers/ ``` endpoint. It is called very often and hangs for ~5sec each time. Not sure why informations about all executors is needed in the first place when opened blue ocean for a given job and a run. Those informations do not seem to be utilised anywhere in the view.
            Hide
            markewaite Mark Waite added a comment -

            Michał Woś sorry that you've encountered the problem. Per the comment from Gavin Mogan, the e Blue Ocean Executor Info plugin is no longer required. You might be able to resolve the issue on your installation by removing the Blue Ocean Executor Info plugin. It is not installed on ci.jenkins.io (likely because Daniel Beck removed it). I was able to remove it from my Jenkins instance without seeing any harmful side effects.

            I agree with Daniel that it would be much better to have an administrative monitor or a Jenkins Health Advisor warning that Blue Ocean Executor Info is not required and may cause performance issues.

            Show
            markewaite Mark Waite added a comment - Michał Woś sorry that you've encountered the problem. Per the comment from Gavin Mogan , the e Blue Ocean Executor Info plugin is no longer required. You might be able to resolve the issue on your installation by removing the Blue Ocean Executor Info plugin. It is not installed on ci.jenkins.io (likely because Daniel Beck removed it). I was able to remove it from my Jenkins instance without seeing any harmful side effects. I agree with Daniel that it would be much better to have an administrative monitor or a Jenkins Health Advisor warning that Blue Ocean Executor Info is not required and may cause performance issues.

              People

              • Assignee:
                Unassigned
                Reporter:
                ojacques Olivier Jacques
              • Votes:
                5 Vote for this issue
                Watchers:
                12 Start watching this issue

                Dates

                • Created:
                  Updated: