Skip to content
This repository was archived by the owner on Sep 21, 2022. It is now read-only.

Auto-Cleanup DB #131

Open
jbspeakr opened this issue Apr 19, 2018 · 0 comments
Open

Auto-Cleanup DB #131

jbspeakr opened this issue Apr 19, 2018 · 0 comments

Comments

@jbspeakr
Copy link
Member

Current Behaviour

Revocation stores data following a more or less sophisticated "bucket algorithm". However, data is never removed from DB which eventually not just results in a filling up DB but also in increased resource usage on all levels.

Expected Behaviour

There is no outdated data stored. This could get achieved by using e.g. TTLs on DB-level or some cleanup worker. This could also help getting rid of that "bucket algorithm" and its arbitrary maxTimeDelta.

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

No branches or pull requests

1 participant