Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

C2D: Storage expiry #735

Open
alexcos20 opened this issue Oct 25, 2024 · 1 comment
Open

C2D: Storage expiry #735

alexcos20 opened this issue Oct 25, 2024 · 1 comment
Assignees
Labels

Comments

@alexcos20
Copy link
Member

All compute engines have compute environments, and each compute environment specifies how long the output produced by a job is held by the node, before being deleted.
When a job expiry is overdue, the node will delete all storage used by that job, and also delete the job record from the database

Task:

  • create a cron that deletes all storage used by expired jobs and deletes the record from db,

Thinks to consider: we have common and most likely specific tasks per each compute engine, so split code in both C2DEngines class and each compute engine class

@paulo-ocean
Copy link
Contributor

inlcuded on PR #705

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants