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

Limit the amount of information kept about old retrievals #760

Open
dirkmc opened this issue Oct 18, 2022 · 0 comments
Open

Limit the amount of information kept about old retrievals #760

dirkmc opened this issue Oct 18, 2022 · 0 comments

Comments

@dirkmc
Copy link
Contributor

dirkmc commented Oct 18, 2022

Currently we store the state transitions for retrieval deals in the datastore in perpetuity. As retrievals increase in frequency this can become very large.
We should put a configurable, soft limit of 7 days on the amount of detailed information we keep about retrieval deals. Probably the simplest mechanism would be to have a background process that periodically cleans up retrievals that are no longer active after the configured duration.

Separately we should also output a retrieval access log, similar to an http access log. The user can choose to rotate / backup this log as they see fit.

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

No branches or pull requests

1 participant