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
            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.
            Hide
            baychris Chris Bayliss added a comment -

            Same issue. Enabling the executor plugin made our Jenkins instance unusable for a couple of days until we tracked the issue down to this bug and disabled it. Our Jenkins master took a massive performance hit with this plugin enabled. Please remove it if it's not required. 

            Show
            baychris Chris Bayliss added a comment - Same issue. Enabling the executor plugin made our Jenkins instance unusable for a couple of days until we tracked the issue down to this bug and disabled it. Our Jenkins master took a massive performance hit with this plugin enabled. Please remove it if it's not required. 
            Hide
            halkeye Gavin Mogan added a comment -

            remove it from what?

            Show
            halkeye Gavin Mogan added a comment - remove it from what?
            Hide
            damien_coraboeuf Damien Coraboeuf added a comment -

            Remove the plugin from your Jenkins installation.

            Show
            damien_coraboeuf Damien Coraboeuf added a comment - Remove the plugin from your Jenkins installation.
            Hide
            danielbeck Daniel Beck added a comment - - edited

            It's no longer a dependency in recent BO releases. You can just click the buttons.

            I don't think the Jenkins project should be able to decide what gets uninstalled on people's instances.

            Show
            danielbeck Daniel Beck added a comment - - edited It's no longer a dependency in recent BO releases. You can just click the buttons. I don't think the Jenkins project should be able to decide what gets uninstalled on people's instances.

              People

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

                Dates

                • Created:
                  Updated: