Bitbucket Server throws "The system CPU load has not been available for <time>. A fixed ticket limit of 3 is in place until the reading is next available"
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Problem
Bitbucket Server is not able to collect the CPU load and is not using the Adaptive Throttling feature to adapt the number of scm tickets to the load of the server.
The following appears in the atlassian-bitbucket.log
1
WARN [Caesium-1-4] c.a.s.i.t.AdaptiveResourceThrottleStrategy [scm-hosting] The system CPU load has not been available for <time>. A fixed ticket limit of 3 is in place until the reading is next availableDiagnosis
Environment
Windows as Operating system
Cause
The user running Bitbucket Server must be a member of the Performance Monitor Users group.
This will allow Bitbucket Server to take full advantage of the Adaptive throttling feature.
Solution
Resolution
Add the user to the Performance Monitor Users group
Restart Bitbucket Server
Was this helpful?