-
Bug
-
Resolution: Fixed
-
High
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
Summary
Scheduled Jobs can be lost track when a database operation fails at the moment the job is claimed by the Scheduler.
This only affects a single-node setup in Server, as in JIRA Data Center the "recovery" job will bring back to memory the lost jobs.
Environment
- JIRA Server (Single Node - Non Data Center)
- JIRA Cloud.
Steps to Reproduce
- Schedule a Job.
- Introduce a breakpoint at CaesiumSchedulerService.executeClusteredJob
- Interrupt database connectivity.
Actual Results
- JIRA will lose track of the job until a restart is performed.
Expected Results.
- JIRA will run the job under its schedule as soon database connectivity is resumed
Notes
This is the root caused behind the issue reported at JSD-3653 but could affect any scheduled job in JIRA.
Workaround
Restart JIRA.
- causes
-
JRACLOUD-61954 Scheduled Jobs Unresponsive/Hangs e.g. mail handlers stop processing emails to create issues due to database connectivity interuptions
- Closed
- is related to
-
JRASERVER-62072 Database connectivity issue causes scheduled jobs to break
- Closed