Handle processing of org related data while they are being moved

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Problem

There are many instance wide operations which process lot of data, not essentially scoped to an organization, eg: inactive_projects_deletion_cron_worker.

If an organization is moved while their data is being processed by such workers, there can be 2 writable destinations (source and target cell) for them. The same problem applies to BBMs, BBOs, CI scheduled pipelines, etc.

Reference links:

We have find a generic way to make these writes idempotent to avoid double work.

Deliverable

  • Document the decision
Edited by 🤖 GitLab Bot 🤖