Bug #13429: Make nodecompliance ttl data - Rudder - Issue Tracker

Actions

Copy link

Bug #13429

closed

Make nodecompliance ttl data

Added by François ARMAND over 6 years ago. Updated over 2 years ago.

Status:

Rejected

Priority:

N/A

Assignee:

Category:

Performance and scalability

Target version:

5.0.17

Pull Request:

Severity:

Major - prevents use of part of Rudder | no simple workaround

UX impact:

User visibility:

Operational - other Techniques | Rudder settings | Plugins

Effort required:

Medium

Priority:

Name check:

Fix check:

Regression:

Description

Related to #13427.

We need to be able to limit drasticly the size of "nodecompliance" table. That table is used for logging the compliance of all nodes at a very precise level but rudder can works without it.

So, user should be able to disable that table if they want, or at least control its ttl at hour level.

Today, the ttl of that data is linked to ttl or report archiving. So we need to split that property appart.

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by François ARMAND over 6 years ago

Related to Bug #13427: On error on nodecompliance SQL, logs are huge added

Actions

Copy link

Updated by François ARMAND over 6 years ago

Status changed from New to In progress

Actions

Copy link

Updated by François ARMAND over 6 years ago

Target version changed from 4.1.15 to 4.3.5
Effort required changed from Very Small to Small
Priority changed from 94 to 80

There was significant code changes between 4.1 and 4.3 and I'm not at all confident about doing any changes in 4.1 in that part - even in 4.3, it may not be trivial.

Actions

Copy link

Updated by François ARMAND over 6 years ago

Status changed from In progress to New
Assignee deleted (~~François ARMAND~~)
Effort required changed from Small to Medium
Priority changed from 80 to 48

So, the code is not that simple to change. It need more work than thought, evec in 4.3.
The reason is that we only have one scheduler for that, and that that TTL would need to live in an other to go below day atomicity. That means an other display, etc.
But it also need code to deal differently with the "0" case, because for that one, we want 0 to mean "don't log at all", not "don't clean at all".
So actually, we need 0 to do a "truncate" or similar if table non-empty, but ALSO to have a check in report processing which don't log at all nodecompliance in that case.

So... All that is needs a couple of days to be taken care of in a released version.

Actions

Copy link

Updated by Vincent MEMBRÉ about 6 years ago

Target version changed from 4.3.5 to 4.3.6

Actions

Copy link

Updated by Vincent MEMBRÉ about 6 years ago

Target version changed from 4.3.6 to 4.3.7
Priority changed from 48 to 47

Actions

Copy link

Updated by Vincent MEMBRÉ about 6 years ago

Target version changed from 4.3.7 to 4.3.8
Priority changed from 47 to 0

Actions

Copy link

Updated by Vincent MEMBRÉ almost 6 years ago

Target version changed from 4.3.8 to 4.3.9

Actions

Copy link

Updated by Alexis Mousset almost 6 years ago

Target version changed from 4.3.9 to 4.3.10

Actions

Copy link

#10

Updated by François ARMAND almost 6 years ago

Target version changed from 4.3.10 to 4.3.11

Actions

Copy link

#11

Updated by Vincent MEMBRÉ over 5 years ago

Target version changed from 4.3.11 to 4.3.12

Actions

Copy link

#12

Updated by François ARMAND over 5 years ago

Severity changed from Minor - inconvenience | misleading | easy workaround to Major - prevents use of part of Rudder | no simple workaround
User visibility changed from Operational - other Techniques | Technique editor | Rudder settings to Operational - other Techniques | Rudder settings | Plugins
Priority changed from 0 to 60