Why is my instance taking so long to start?

Issue

After the December upgrade CloudBees CI (CloudBees Core) 2.263.1.2, we have observed that our controllers take more time to startup. In some cases, the startup operation does not finish.

Environment

Explanation

The observed behavior is the result of one of the scenarios listed below:

  • Scenario A - First upgrade to December or January release with 1.x of the plugin already installed. Upgrade to the December or the January release automatically upgrades the plugin to 2.0 / 2.2. Issue may occur at the next restart of the controller after upgrading.

  • Scenario B - Upgrade from December -> January release. Upgrade to the January release automatically upgrades the plugin from version 2.0 to version 2.2. Issue may occur at the restart of the controller as it completes the upgrade process.

  • Scenario C - On December / January release and you want to install the new plugin. Version 2.0 or 2.2 of the plugin will be installed. Issue may occur at the next restart of the controller.

Resolution

The plugin collects asynchronously the information while the instance is running and writes it down to a file. This file is parsed during the startup of a controller and can take several minutes or much longer on big instances.

In order to completely solve the issue, the best way to go forward is to upgrade the plugin to version 2.6, included in the February release CloudBees CI (CloudBees Core) 2.263.4.1, improves the way that the loading process works.

  • Case A: You can upgrade to February release

  • In the February release of CloudBees CI (2.263.4.1) there are two fixes to resolve this issue. The plugin usage analysis file is now loaded asynchronously, therefore it no longer blocks the other startup processes. Loading of this file is made more efficient by replacing json-lib with jackson. The plugin version containing these fixes is v2.6.

  • Case B: You cannot upgrade to February release, or you cannot upgrade to CloudBees Plugin Usage Analyzer plugine 2.6

  • Disable the plugin usage analyzer plugin (recommended by the Support Team prior to February release)

  • Or you can remove the analysis.json file before each restart

Tested product/plugin versions

References

Have more questions?

0 Comments

Please sign in to leave a comment.