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

Cache clean for items older than x #5095

Closed
dtrudg opened this issue Mar 6, 2020 · 1 comment · Fixed by #5249
Closed

Cache clean for items older than x #5095

dtrudg opened this issue Mar 6, 2020 · 1 comment · Fixed by #5249
Assignees
Labels
Regression Issues which describes regressions in Singularity
Milestone

Comments

@dtrudg
Copy link
Contributor

dtrudg commented Mar 6, 2020

#5088 disables the code to remove a specific cache item.

This will be returned in a future refactor that moves the body of the cache deletion code into the cache package, out of the CLI.

@dtrudg dtrudg added the Regression Issues which describes regressions in Singularity label Mar 6, 2020
@dtrudg dtrudg added this to the 3.6.0 milestone Mar 6, 2020
@dtrudg dtrudg self-assigned this Mar 6, 2020
@dtrudg dtrudg changed the title Return cache clean of a specific item after #5088 Cache clean for items older than x Apr 22, 2020
@dtrudg
Copy link
Contributor Author

dtrudg commented Apr 22, 2020

Changing this issue to reflect that after discussion it has been decided to implement cache clean of items older than a specified duration. The new cache format doesn't save the names of any items - only their hashes which are not really useful to clean specifically. This was also mostly the case previously as blob and oci-tmp caches used hashes for entry names.

The though of doing it by age instead has also come up in discussion on slack more than once. It seems generally more useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Regression Issues which describes regressions in Singularity
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant