Actions
Bug #15413
closedAutovacuum may never finish, or take more than one day, on busy Rudder instance, because of resources attrition
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
In https://issues.rudder.io/issues/14336 we introduced autovacuum on most table, and especialy ruddersysevents
Problem is postgres cannot keep up with the rate of data on this table, and on a busy instance, it can take more than a day. In result, it block the standart vacuum made every night, and so disk space grows out of limit
In this case, the only solution is to
ALTER TABLE ruddersysevents SET (autovacuum_enabled = false);
select pg_terminate_backend(<autovacuum id>);
and hope the database can recover
we need to remove this autovacuum as it is too risky
Note, it may be the cause of https://issues.rudder.io/issues/14789
Actions