Poms should keep a list of job launches requested while job launches are "held"
Poms should keep a list of job launches requested while job launches are "held",
and then run them at some rate when job launches are un-held (possibly controlled by a flag on the job-type/campaign-definition) so we don't lose submissions.
#2 Updated by Marc Mengel almost 4 years ago
- Assignee set to Stephen White
This would need a held_launches table, with parameters for launch_jobs:
- campaign_id (campaign foriegn key->Campaigns)
- dataset_override (Nullable string)
- parent_task_id (Nullable foreign key->tasks)
Then when launch_jobs is called, it would queue them if jobs are held, and
when job launches are un-held, we could trigger these at some rate.
Assigning to Steven for database table, he can dump it on me when its done.