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

High master CPU usage introduced by Blue Ocean 1.14.0

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • blueocean-plugin
    • None
    • BlueOcean 1.14.0
      Jenkins 1.168
    • 1.15.0

      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.

          [JENKINS-56773] High master CPU usage introduced by Blue Ocean 1.14.0

          Daniel Beck added a comment -

          this one deserves a separate treatment in my opinion

          I would rather not add an elaborate and certain to be controversial feature to Jenkins (core) for it to be used only once for an issue that was resolved a year ago, and then never again.

          It would be plenty good enough for new Blue Ocean releases to show a warning to administrators if this plugin is still installed (and enabled), but that's up to its maintainers.

           

          Daniel Beck added a comment - this one deserves a separate treatment in my opinion I would rather not add an elaborate and certain to be controversial feature to Jenkins (core) for it to be used only once for an issue that was resolved a year ago, and then never again. It would be plenty good enough for new Blue Ocean releases to show a warning to administrators if this plugin is still installed (and enabled), but that's up to its maintainers.  

          Jesse Glick added a comment -

          Should suffice for BO maintainers (halkeye? olamy?) to just cut a “tombstone” release of this plugin with zero code and prominently marked as deprecated. Then people who simply update all plugins routinely would get the tombstone and no longer encounter issues; they could uninstall the plugin at some point for purposes of cleanup.

          Jesse Glick added a comment - Should suffice for BO maintainers ( halkeye ? olamy ?) to just cut a “tombstone” release of this plugin with zero code and prominently marked as deprecated. Then people who simply update all plugins routinely would get the tombstone and no longer encounter issues; they could uninstall the plugin at some point for purposes of cleanup.

          Daniel Beck added a comment -

          marked as deprecated

          Good point, Jenkins 2.248 and newer also prominently shows which plugins are labeled deprecated; we could add this one: https://github.com/jenkins-infra/update-center2/pull/451

          (TBH it seems crazy to me that it's still getting new releases because it's still in the multimodule project…)

           

          Daniel Beck added a comment - marked as deprecated Good point, Jenkins 2.248 and newer also prominently shows which plugins are labeled deprecated; we could add this one: https://github.com/jenkins-infra/update-center2/pull/451 (TBH it seems crazy to me that it's still getting new releases because it's still in the multimodule project…)  

          ethorsa added a comment -

          I can't remove the plugin since it's still shown as a dependency of Blue Ocean. The enable and uninstall control are both greyed out. The Plugin is marked as deprecated though.

          Jenkins 2.249.2, Blue Ocean / Blue Ocean Executor Info v1.24.2.

          ethorsa added a comment - I can't remove the plugin since it's still shown as a dependency of Blue Ocean. The enable and uninstall control are both greyed out. The Plugin is marked as deprecated though. Jenkins 2.249.2, Blue Ocean / Blue Ocean Executor Info v1.24.2.

          Gavin Mogan added a comment -

          Please open a new issue if this is happening again, reviving old bugs is not going to get things addressed.

          Gavin Mogan added a comment - Please open a new issue if this is happening again, reviving old bugs is not going to get things addressed.

          Olivier Lamy added a comment - - edited

          The plugin does NOTHING now and will be removed with next release.

          Olivier Lamy added a comment - - edited The plugin does NOTHING now and will be removed with next release.

          Mark Waite added a comment - - edited

          I'm seeing the same condition that is described by ethorsa. Prior to Blue Ocean 1.24.1, I was able to uninstall the blueocean executor info plugin so that I could avoid this issue. With the release of blueocean I'm unable to uninstall the blueocean executor info plugin.

          I'm not seeing any issue from the blueocean-executor-info plugin itself, since (as noted by olamy) it now does nothing. It is an empty plugin.

          I assume the next release of Blue Ocean (possibly 1.24.3) will remove the dependency on blueocean executor info plugin so that I can uninstall it. Until then, the admin monitor warning will continue to be visible that tells me I have a deprecated plugin in my Jenkins installation. I prefer to have no admin monitors raising alerts on my Jenkins installation, but there does not appear to be any way to resolve this one other than waiting for the next release of Blue Ocean.

          Mark Waite added a comment - - edited I'm seeing the same condition that is described by ethorsa . Prior to Blue Ocean 1.24.1, I was able to uninstall the blueocean executor info plugin so that I could avoid this issue. With the release of blueocean I'm unable to uninstall the blueocean executor info plugin. I'm not seeing any issue from the blueocean-executor-info plugin itself, since (as noted by olamy ) it now does nothing. It is an empty plugin. I assume the next release of Blue Ocean (possibly 1.24.3) will remove the dependency on blueocean executor info plugin so that I can uninstall it. Until then, the admin monitor warning will continue to be visible that tells me I have a deprecated plugin in my Jenkins installation. I prefer to have no admin monitors raising alerts on my Jenkins installation, but there does not appear to be any way to resolve this one other than waiting for the next release of Blue Ocean.

          Olivier Lamy added a comment -

          I agree it's annoying... I will cut a new release next week so people will have enough time to notice this plugin has been deprecated

          Olivier Lamy added a comment - I agree it's annoying... I will cut a new release next week so people will have enough time to notice this plugin has been deprecated

          Paul Bruce added a comment -

          Also getting this in the past few days. To olamy 's point, would like guidance on what to do here.

          Paul Bruce added a comment - Also getting this in the past few days. To olamy 's point, would like guidance on what to do here.

          Mark Waite added a comment -

          paulsbruce if you've upgraded to blue ocean 1.24.2 and restarted your Jenkins server since the upgrade, then the blueocean-executor-info plugin described in this bug report cannot be causing the high CPU usage. With release 1.24.2, the blueocean-executor-info plugin contains no code.

          The contents of the plugin file (hpi / jpi file) are:

          M Filemode      Length  Date         Time      File
          - ----------  --------  -----------  --------  --------------------------------------------------------------------------
            drwxr-xr-x         0  27-Oct-2020  08:59:58  META-INF/
            -rw-r--r--       855  27-Oct-2020  08:59:56  META-INF/MANIFEST.MF
            drwxr-xr-x         0  27-Oct-2020  08:59:58  WEB-INF/
            drwxr-xr-x         0  27-Oct-2020  08:59:58  WEB-INF/lib/
            -rw-r--r--       531  27-Oct-2020  08:59:58  WEB-INF/licenses.xml
            -rw-r--r--      3648  27-Oct-2020  08:59:58  WEB-INF/lib/blueocean-executor-info.jar
            drwxr-xr-x         0  27-Oct-2020  08:59:58  META-INF/maven/
            drwxr-xr-x         0  27-Oct-2020  08:59:58  META-INF/maven/io.jenkins.blueocean/
            drwxr-xr-x         0  27-Oct-2020  08:59:58  META-INF/maven/io.jenkins.blueocean/blueocean-executor-info/
            -rw-r--r--      4010  27-Oct-2020  08:59:56  META-INF/maven/io.jenkins.blueocean/blueocean-executor-info/pom.xml
            -rw-r--r--       130  27-Oct-2020  08:59:58  META-INF/maven/io.jenkins.blueocean/blueocean-executor-info/pom.properties
          - ----------  --------  -----------  --------  --------------------------------------------------------------------------
                            9174                         11 files
          

          The contents of the jar file packaged in that plugin are:

          M Filemode      Length  Date         Time      File
          - ----------  --------  -----------  --------  --------------------------------------------------------------------------
            drwxr-xr-x         0  27-Oct-2020  08:59:58  META-INF/
            -rw-r--r--       855  27-Oct-2020  08:59:56  META-INF/MANIFEST.MF
            -rw-r--r--        93  27-Oct-2020  08:59:56  jenkins-js-extension.json
            -rw-r--r--      1290  27-Oct-2020  08:36:28  package.json
            -rw-r--r--        70  27-Oct-2020  08:59:56  index.jelly
            drwxr-xr-x         0  27-Oct-2020  08:59:58  META-INF/maven/
            drwxr-xr-x         0  27-Oct-2020  08:59:58  META-INF/maven/io.jenkins.blueocean/
            drwxr-xr-x         0  27-Oct-2020  08:59:58  META-INF/maven/io.jenkins.blueocean/blueocean-executor-info/
            -rw-r--r--      4010  27-Oct-2020  08:59:56  META-INF/maven/io.jenkins.blueocean/blueocean-executor-info/pom.xml
            -rw-r--r--       130  27-Oct-2020  08:59:58  META-INF/maven/io.jenkins.blueocean/blueocean-executor-info/pom.properties
          - ----------  --------  -----------  --------  --------------------------------------------------------------------------
                            6448                         10 files
          

          If you're seeing high cpu usage with blue ocean 1.24.2 installed, it is not a result of the blueocean-executor-info plugin described in this bug report.

          Mark Waite added a comment - paulsbruce if you've upgraded to blue ocean 1.24.2 and restarted your Jenkins server since the upgrade, then the blueocean-executor-info plugin described in this bug report cannot be causing the high CPU usage. With release 1.24.2, the blueocean-executor-info plugin contains no code. The contents of the plugin file (hpi / jpi file) are: M Filemode Length Date Time File - ---------- -------- ----------- -------- -------------------------------------------------------------------------- drwxr-xr-x 0 27-Oct-2020 08:59:58 META-INF/ -rw-r--r-- 855 27-Oct-2020 08:59:56 META-INF/MANIFEST.MF drwxr-xr-x 0 27-Oct-2020 08:59:58 WEB-INF/ drwxr-xr-x 0 27-Oct-2020 08:59:58 WEB-INF/lib/ -rw-r--r-- 531 27-Oct-2020 08:59:58 WEB-INF/licenses.xml -rw-r--r-- 3648 27-Oct-2020 08:59:58 WEB-INF/lib/blueocean-executor-info.jar drwxr-xr-x 0 27-Oct-2020 08:59:58 META-INF/maven/ drwxr-xr-x 0 27-Oct-2020 08:59:58 META-INF/maven/io.jenkins.blueocean/ drwxr-xr-x 0 27-Oct-2020 08:59:58 META-INF/maven/io.jenkins.blueocean/blueocean-executor-info/ -rw-r--r-- 4010 27-Oct-2020 08:59:56 META-INF/maven/io.jenkins.blueocean/blueocean-executor-info/pom.xml -rw-r--r-- 130 27-Oct-2020 08:59:58 META-INF/maven/io.jenkins.blueocean/blueocean-executor-info/pom.properties - ---------- -------- ----------- -------- -------------------------------------------------------------------------- 9174 11 files The contents of the jar file packaged in that plugin are: M Filemode Length Date Time File - ---------- -------- ----------- -------- -------------------------------------------------------------------------- drwxr-xr-x 0 27-Oct-2020 08:59:58 META-INF/ -rw-r--r-- 855 27-Oct-2020 08:59:56 META-INF/MANIFEST.MF -rw-r--r-- 93 27-Oct-2020 08:59:56 jenkins-js-extension.json -rw-r--r-- 1290 27-Oct-2020 08:36:28 package.json -rw-r--r-- 70 27-Oct-2020 08:59:56 index.jelly drwxr-xr-x 0 27-Oct-2020 08:59:58 META-INF/maven/ drwxr-xr-x 0 27-Oct-2020 08:59:58 META-INF/maven/io.jenkins.blueocean/ drwxr-xr-x 0 27-Oct-2020 08:59:58 META-INF/maven/io.jenkins.blueocean/blueocean-executor-info/ -rw-r--r-- 4010 27-Oct-2020 08:59:56 META-INF/maven/io.jenkins.blueocean/blueocean-executor-info/pom.xml -rw-r--r-- 130 27-Oct-2020 08:59:58 META-INF/maven/io.jenkins.blueocean/blueocean-executor-info/pom.properties - ---------- -------- ----------- -------- -------------------------------------------------------------------------- 6448 10 files If you're seeing high cpu usage with blue ocean 1.24.2 installed, it is not a result of the blueocean-executor-info plugin described in this bug report.

            olamy Olivier Lamy
            ojacques Olivier Jacques
            Votes:
            7 Vote for this issue
            Watchers:
            17 Start watching this issue

              Created:
              Updated:
              Resolved: