You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 21, 2022. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: