Hi,
We’ve been running Boundary for awhile and seems that the boundary DB size keeps growing constantly:
- Database boundary size: 2.36GB
- Largest tables:
wh_session_connection_accumulating_fact: 761.15MB
wh_session_accumulating_fact: 655.16MB
auth_token: 374.95MB
wh_auth_token_accumulating_fact: 262.62MB
auth_token_deleted: 160.69MB
…
What would be the recommended process on how to cleanup DB (without breaking the Boundary)?
Can we cleanup the “accumulating_fact” tables with something simple as (for example):
DELETE FROM wh_session_connection_accumulating_fact WHERE created_at < NOW() - INTERVAL ‘180 days’;
DELETE FROM wh_session_accumulating_fact WHERE created_at < NOW() - INTERVAL ‘180 days’;
DELETE FROM wh_auth_token_accumulating_fact WHERE created_at < NOW() - INTERVAL ‘180 days’;
VACUUM FULL;
And could the “auth_token” and “auth_token_deleted” tables be cleaned up same way?
Ps. Would it be possible to get some automation that would clean up the old entries from the DB?
PPs. Current boundary server version: 0.18.2