Bug #11591
closed
Tidy expected reports does have a too big TTL
Added by Janos Mattyasovszky about 7 years ago.
Updated about 7 years ago.
Category:
System techniques
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Very Small
Description
I have had a broken agent some about ~1.5 Month ago, and therefore my state directory was spammed with /var/rudder/cfengine-community/state/rudder_expected_reports.*.csv.*
I had about 17k files matching that, but none were removed due to the default TTL is 90+ days via CFENGINE_OUTPUTS_TTL
.
The agent run took quite some additional time (didn't measure it really).
It does not really make too much sense to keep more than the latest (or maybe 1 day?) laying around.
- Category changed from Agent to System techniques
I don't see how it could be useful either. We need to keep the recent ones in case we have several parallel runs, but 1 day is more than enough.
We might have run into this more often without understanding.
Interesting, and I think should be higher prio?
- Effort required set to Very Small
- Priority changed from 32 to 49
Let's fix this TTL to 1 day non configurable
- Target version set to 4.1.8
- Status changed from New to In progress
- Assignee set to Alexis Mousset
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1207
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.8 and 4.2.1 which were released today.
Also available in: Atom
PDF