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

High master CPU usage introduced by Blue Ocean 1.14.0

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • blueocean-plugin
    • None
    • BlueOcean 1.14.0
      Jenkins 1.168
    • 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

            olamy Olivier Lamy added a comment - - edited

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

            olamy Olivier Lamy added a comment - - edited The plugin does NOTHING now and will be removed with next release.
            markewaite 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.

            markewaite 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.
            olamy 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

            olamy 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
            paulsbruce 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.

            paulsbruce 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.
            markewaite 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.

            markewaite 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.

            People

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

              Dates

                Created:
                Updated:
                Resolved: