Bug #15413
closedAutovacuum may never finish, or take more than one day, on busy Rudder instance, because of resources attrition
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
Updated by Nicolas CHARLES over 5 years ago
- Related to Bug #14336: Rudder database grows with time because of defaults values for autovacuum that don't fit our needs added
Updated by Nicolas CHARLES over 5 years ago
- Related to Bug #14789: Postgres fills up and can't be vaccumed added
Updated by Nicolas CHARLES over 5 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES over 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder/pull/2376
Updated by Nicolas CHARLES over 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|aca2de0c03f7e1b3df3cba8c045b94b090982bdf.
Updated by Nicolas CHARLES about 5 years ago
- Fix check changed from To do to Checked
Updated by Alexis Mousset about 5 years ago
- Name check changed from To do to Reviewed
Updated by Vincent MEMBRÉ about 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.13 which was released today.