Medium Issue Summary
Every time a Jira node is properly stopped, the schedules for this job is removed: com.atlassian.greenhopper.service.sprint.services.SprintAutoStartStopJob
While this makes sense for disabling plugins from the UPM UI, this may break important the functionality for those jobs whenever a node is stopped and not started again.
Steps to Reproduce
- Set up a Jira DC with 2 nodes or more;
- Check "Parallel Sprints" in Jira Software Configuration
- Stop a node.
Expected Results
Everything remains working as normal
Actual Results
The job schedule for com.atlassian.greenhopper.service.sprint.services.SprintAutoStartStopJob is removed:
We can see Jira doing it in the logs:
2024-08-13 11:34:31,850 FelixShutdown INFO [com.atlassian.greenhopper.Launcher] Unscheduling Jira Agile jobs... 2024-08-13 11:34:31,850 FelixShutdown INFO [service.sprint.services.SprintAutoStartStopScheduler] [SPRINT-AUTO-START-STOP] Starting to unschedule a SprintAutoStartStopJob... 2024-08-13 11:34:31,853 FelixShutdown INFO [service.sprint.services.SprintAutoStartStopScheduler] [SPRINT-AUTO-START-STOP] SprintAutoStartStopJob has been unscheduled.
Workaround
- When stopping a node permanently, stop it using
kill -9 <pid>
- Or restart one remaining node after the removal. Jira will always create the schedules again when Jira Software starts up
- Disabling "Parallel Sprints" and re-enabling it recreates the job
- has a derivative of
-
JSDSERVER-15502 Assets stale progress cleanup job (AssetsProgressCleanupJob) is unscheduled on clustered Data Center if one of the nodes is stopped
-
- Gathering Impact
-
- blocks
-
ACE-6010 You do not have permission to view this issue
- causes
-
ACE-5884 You do not have permission to view this issue
- is resolved by
-
JSWDC-63 You do not have permission to view this issue
- relates to
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-26067] Stopping a node removes the SprintAutoStartStopJob job
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
| Current Status |
New:
{panel:title=Atlassian Update – 19 December 2024|borderStyle=solid|borderColor=#deebff | titleBGColor=#deebff | bgColor=#deebff}
Dear Customers, Thank you for reporting this issue. In the last weeks we have been working hard on fixing it. Since now Jira will recognise other ALIVE(with heartbeat) and ACTIVE nodes in the cluster. If such exist it will not unschedule the job. Best regards. Daniel Dudziak Principal Software Engineer {panel} |
| Fix Version/s | New: 10.4.0 [ 110311 ] |
| Status | Original: In Progress [ 3 ] | New: Waiting for Release [ 12075 ] |
| Assignee | New: Stasiu [ ddudziak ] |
| Status | Original: Gathering Impact [ 12072 ] | New: In Progress [ 3 ] |
| Remote Link | Original: This issue links to "JSWDC-63 (Bulldog)" [ 969976 ] | New: This issue links to "JSWDC-63 (JIRA Server (Bulldog))" [ 969976 ] |
| Remote Link | New: This issue links to "JSWDC-63 (Bulldog)" [ 969976 ] |
| Labels | Original: ACE-6010 FY25NNB FY25NNBN NNB3 | New: ACE-6010 FY25NNB NNB3 |
| Labels | Original: ACE-6010 FY25NNB NNB3 | New: ACE-6010 FY25NNB FY25NNBN NNB3 |