HealthCheck: Scheduler
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles 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
Overview
Cluster replication relies on a scheduler (currently this is handled by Quartz) to run tasks to keep the nodes in sync. The Scheduler causes events to fire at designated times, similar to cron or Windows Task Manager.
Understanding the Results
| Icon | Result | What this means |
|---|---|---|
 | The health check passed successfully. | The Scheduling Service is running. |
 | Task scheduler is not running - <scheduler state> | The task scheduler is not reported in the expected state (STARTED). |
Troubleshooting
| Problem | Suggestion |
|---|---|
| If the scheduler is not running. | The only way to restart the scheduler is to restart the instance. It's recommended to collect some thread dumps prior to doing so (if Atlassian Support will be contacted) as per Generating a Thread Dump. |
Providing Information to Support
In case you are unable to troubleshoot and fix the problem by yourself, please create a support ticket at support.atlassian.com and attach the following information to the ticket:
- Take a Screenshot of the Health Check results.
- Collect a Support ZIP from each of the Data Centre nodes.
- Any collected information from the suggestions in this document.