Project

General

Profile

Actions

Bug #14003

closed

nodecompliancelevels is not purged

Added by Alexis Mousset about 6 years ago. Updated about 6 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
-
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

On a 5.0 server, I have a nodecompliancelevels table containing old entries, and the table does not seems to be archived/purged.

archivedruddersysevents is correctly cleaned though.

rudder=> select min(executiontimestamp) from archivedruddersysevents;
          min           
------------------------
 2018-12-10 00:00:12+01
(1 row)
rudder=> select min(runtimestamp) from nodecompliancelevels;
          min           
------------------------
 2018-12-04 00:00:01+01
(1 row)
rudder=> select * from archivedreportsexecution;
 nodeid | date | complete | nodeconfigid | insertionid 
--------+------+----------+--------------+-------------
(0 rows)
rudder=> select min(begindate) from archivednodeconfigurations;
            min             
----------------------------
 2018-12-10 15:09:45.282+01
(1 row)


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #15372: Missing logs on NodeCompliance archive/deletionReleasedFrançois ARMANDActions
Actions #1

Updated by Alexis Mousset about 6 years ago

  • Description updated (diff)
Actions #2

Updated by Alexis Mousset about 6 years ago

  • Description updated (diff)
Actions #3

Updated by Nicolas CHARLES about 6 years ago

  • Status changed from New to Rejected

ok, this is cleaned, based on parameter
rudder.batch.reportscleaner.compliancelevels.delete.TTL

default value is 15, that is why it grew out quite a lot

Actions #4

Updated by Nicolas CHARLES over 5 years ago

  • Related to Bug #15372: Missing logs on NodeCompliance archive/deletion added
Actions

Also available in: Atom PDF