Project

General

Profile

Bug #15413

Autovacuum may never finish, or take more than one day, on busy Rudder instance, because of resources attrition

Added by Nicolas CHARLES 3 months ago. Updated 2 months ago.

Status:
Released
Priority:
N/A
Category:
System integration
Target version:
Severity:
User visibility:
Effort required:
Priority:
0

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


Subtasks

Bug #15416: Create migration script to remove autovacuum for ruddersyseventsReleasedAlexis MOUSSETActions
Bug #15653: Missing migration script for vacuum changeReleasedAlexis MOUSSETActions

Related issues

Related to Rudder - Bug #14336: Rudder database grows with time because of defaults values for autovacuum that don't fit our needsReleasedActions
Related to Rudder - Bug #14789: Postgres fills up and can't be vaccumedReleasedActions

Associated revisions

Revision aca2de0c (diff)
Added by Nicolas CHARLES 3 months ago

Fixes #15413: Autovacuum may never finish, or take more than one day, on busy Rudder instance, because of resources attrition

History

#1

Updated by Nicolas CHARLES 3 months ago

  • Related to Bug #14336: Rudder database grows with time because of defaults values for autovacuum that don't fit our needs added
#2

Updated by Nicolas CHARLES 3 months ago

  • Related to Bug #14789: Postgres fills up and can't be vaccumed added
#3

Updated by Nicolas CHARLES 3 months ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES
#4

Updated by Nicolas CHARLES 3 months 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
#5

Updated by Nicolas CHARLES 3 months ago

  • Status changed from Pending technical review to Pending release
#8

Updated by Vincent MEMBRÉ 2 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.13 which was released today.

Also available in: Atom PDF