Skip to content

[meta] Background worker issues #11528

@SchrodingersGat

Description

@SchrodingersGat

A couple of recent issues have highlighted some shortcomings of the existing background worker implementation - especially for long-running complex processes which touch the database many times.

Related Issues

Problem Overview

In short:

  • The background worker is not very stable on a sqlite backend due to db locks / concurrency issues
  • There is no way for users to monitor the progress of a long-running task - or to determine if it passed or failed
  • Some background processes are split into multiple other processes - which makes concurrency issues worse
  • Some tasks are run in the "wrong order" - task success is saved first, before the long running processes are actually performed

Fixes

Metadata

Metadata

Assignees

No one assigned

    Labels

    CICI / unit testing ecosystemUser InterfaceRelated to the frontend / User InterfaceapiRelates to the APIbugIdentifies a bug which needs to be addressedrefactor

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions