Skip to content

Update StuckExportJobsWorker to not fail parallel export jobs

What does this MR do and why?

This MR updates StuckExportJobsWorker to not mark 'started' export job as failed when:

  1. It has relation_exports association records, which indicates this is a parallel export
  2. export_job.created_at is still less than 6.hours.ago

It fixes a situation when parallel_project_export feature flag is enabled (currently disabled everywhere) and we initiate a big project export. In this scenario, the following problem occurs:

  1. A job completes and marks export job as started
  2. Relation export jobs for each of the relations are in progress
  3. A StuckExportJobsWorker cron job kicks in (every 30 minutes), see that there's a job completed but export status is started and considers it to be in a wrong state. Marks it as failed

Mentions #461242 (closed)

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Edited by George Koltsov

Merge request reports