CPU Running at 100% Utilization Consistently
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
Problem
Fisheye server appears to be very busy with the CPU pegged at 100% utilization. There are no other applications running on the machine that appear to be consuming resources. There are no apparent exceptions reported in the Fisheye logs.
Cause
The FISHEYE_INST/config.xml has a similar configuration:
config.xml
1
2
3
4
5
<resources>
<incrementalIndexThreads max="30"/>
<initialIndexThreads max="300"/>
</resources>
<crowd auto-add="true" resync="true" refreshExistingUsers="true" sso-enabled="true" resyncPeriod="1 hour" jiraInstance="false">Resolution
The number of incremental and initial indexing threads configured is too excessive which will make the system very busy. The recommended count is 3 each for these threads, as documented here. Reduce the number of configured initial and incremental threads to 3 each and monitor the instance.
Automatic synchronization should be turned OFF for instances with large external user repositories. Having this property turned ON will add extra overhead on the system. Turn this property OFF and use the manual sync option as and when required. More details on how to manage synchronization for large user repositories are here.
Was this helpful?