-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
5.17.0, 5.17.2
-
1
-
Severity 2 - Major
-
0
-
Issue Summary
During Jira Service Management shutdown process, some plugins may be disabled.
As part of the disable process, some plugins may unschedule related jobs.
During a graceful shutdown of a single node of a JSM DC cluster, it may unschedule the AssetsProgressCleanupJob for the entire cluster.
If this is not part of a node restart, the job will be missing until a new node is started.
Steps to Reproduce
- Install a vanilla instance of Jira Service Management.
- This should be a clustered data center instance with at least 2 nodes.
- Go to Administration > System > Scheduler details.
- Search for AssetsProgressCleanupJob and note the schedule exists.
- Stop only one of the nodes of the JSM DC cluster.
- Jira should be gracefully stopped without killing the Java process.
- Go to Administration > System > Scheduler details.
- Search for AssetsProgressCleanupJob.
Expected Results
The AssetsProgressCleanupJob schedule still exists.
Actual Results
The AssetsProgressCleanupJob scheduled job is not on the list anymore.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available.
- derived from
-
JSWSERVER-26067 Stopping a node removes the SprintAutoStartStopJob job
- Waiting for Release
- blocks
-
ACE-6010 Loading...
- causes
-
ACE-5884 Loading...
- links to