Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
8.14.0, 8.20.0, 9.0.0, 9.4.0, 9.12.0, 9.15.0
-
8.14
-
1
-
Severity 3 - Minor
-
Description
Issue Summary
Jira data pipeline may still report a job a started even if it's not running anymore.
This scenario impacts the ability of running subsequent jobs, even though it wasn't previously on status of failure.
Data pipeline should be able to identify a job isn't running anymore, marking it as incomplete, and allowing new jobs to start.
Steps to Reproduce
- Install a vanilla instance of Jira Software.
- This was validated on JSW DC versions 9.4.18 and 9.15.0.
- Make sure you have a fair amount of issues so the data pipeline job takes some time.
- The test was conducted on an instance with ~200k issues.
- Start a new data pipeline job by running a REST API call similar to the below.
JIRA_BASE_URL=jira_base_url JIRA_USER=admin JIRA_USER_PWD=admin curl -u ${JIRA_USER}:${JIRA_USER_PWD} -X POST \ -H 'Accept: application/json' \ ${JIRA_BASE_URL}'/rest/datapipeline/latest/export?fromDate=2023-12-31T00:00:00Z&forceExport=true'
- Kill the Jira process while the data pipeline job is running.
- Start Jira.
- Trigger a new data pipeline job or let it run through the schedule.
Expected Results
Jira identifies the previous data pipeline job isn't running anymore and properly starts the new job.
Actual Results
The previous data pipeline job status is still reported as started and the new one is reported as failed.
Workaround
To allow new jobs running, cancel the job that is still reported as running to allow new jobs starting.
- Get the job ID of the one still reported as started from the UI.
- In this example, the job ID is 1.
- Run the following REST API to mark the job as cancelled.
JIRA_BASE_URL=jira_base_url JIRA_USER=admin JIRA_USER_PWD=admin JOB_ID=1 curl -v -s -u ${JIRA_USER}:${JIRA_USER_PWD} -X DELETE \ ${JIRA_BASE_URL}'/rest/datapipeline/latest/export?jobId='${JOB_ID}
- Monitor the data pipeline admin page to ensure the new scheduled job will start as expected.