Page MenuHomeSoftware Heritage

Failure mode for Vault tasks
Closed, MigratedEdits Locked

Description

Vault cooking tasks need to be able to "fail" for multiple reasons:

  • the bundle can't be cooked (it exceeds some limitations like bundle size etc),
  • the bundle temporarily can't be cooked (no space left on device because we did something wrong somewhere?)
  • any unplanned exception that happens in the cooker (a bug in our code)

There are multiple ways to do this, the important question is to figure out when we should allow a failed bundle to be re-cooked.

Event Timeline

seirl triaged this task as Normal priority.Nov 13 2017, 1:31 PM
seirl created this task.
zack added a project: Restricted Project.Jan 3 2018, 3:13 PM
zack moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Jan 3 2018, 3:27 PM

For now we allow to retry as soon as the bundle status is set as "failed". rDVAU3a3c337107e6 implements the failure state.

seirl moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Jan 12 2018, 2:42 PM