Project

General

Profile

Actions

Idea #9277

closed

[Crunch2] System-owned container outputs should be garbage-collected

Added by Peter Amstutz over 8 years ago. Updated almost 8 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
API
Target version:
Start date:
02/16/2017
Due date:
Story points:
0.5
Release:
Release relationship:
Auto

Description

Background

When a container finishes, crunch-run creates an output collection and records its PDH in the container record.

On the API server, the container update triggers a hook that creates one copy of the output collection for each of N container requests that have been waiting on this container.

The original output collection is owned by root and there is no cleanup process has trash_at set to now+defaultTrashLifetime.

Proposed fix

In crunch-run, create the output collection with trash_at=now.

In the API server hook that creates a collection for each relevant container request, when looking up the container output manifest, make sure to include trashed collections in the search.


Subtasks 2 (0 open2 closed)

Task #11107: Review 9277-trash-container-outputsResolvedRadhika Chippada02/16/2017Actions
Task #11164: Review 9277-container-outputResolvedPeter Amstutz02/16/2017Actions

Related issues 3 (1 open2 closed)

Related to Arvados - Idea #9278: [Crunch2] Document/fix handling of collections with non-nil expires_at fieldIn ProgressActions
Related to Arvados - Feature #11100: [CWL] Intermediary collection handling can be specifiedResolvedPeter Amstutz03/30/2017Actions
Has duplicate Arvados - Feature #11064: [Crunch2] crunch-run expires output collection immediatelyDuplicateActions
Actions

Also available in: Atom PDF