Project

General

Profile

Actions

Bug #15416

closed

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

Create migration script to remove autovacuum for ruddersysevents

Added by Nicolas CHARLES over 4 years ago. Updated over 4 years ago.

Status:
Released
Priority:
N/A
Category:
System integration
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Error - Fixed
Regression:

Subtasks 1 (0 open1 closed)

Bug #15653: Missing migration script for vacuum changeReleasedAlexis MoussetActions
Actions #1

Updated by Nicolas CHARLES over 4 years ago

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

Updated by Nicolas CHARLES over 4 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-packages/pull/2023
Actions #3

Updated by Nicolas CHARLES over 4 years ago

  • Status changed from Pending technical review to Pending release
Actions #4

Updated by François ARMAND over 4 years ago

  • Subject changed from Create migration script for parent ticket to Create migration script to remove autovacuum for ruddersysevents
Actions #5

Updated by François ARMAND over 4 years ago

  • Fix check changed from To do to Error - Blocking

File "dbMigration-5.0.x-5.0.13-remove-autovacuum-on-ruddersysevents.sql" is missing

Actions #6

Updated by François ARMAND over 4 years ago

  • Fix check changed from Error - Blocking to Error - Fixed
Actions #7

Updated by Vincent MEMBRÉ over 4 years ago

  • Status changed from Pending release to Released

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

Actions

Also available in: Atom PDF