User story #4152
closed
Reduce default maximum days of reports retained
Description
We have two level of storing node's agent execution reports:
- the main database
- an archive one.
Today, we use a loooong duration for the main database (30 days?), what is not necessary and has bad impacts on performance. A few hours, maximum 36 (so that we have detailed execution reports for the last night) should be sufficient.
The archive retention duration can be kept to the big value it has today.
Updated by François ARMAND about 11 years ago
- Target version changed from Ideas (not version specific) to 2.9.0~rc1
Updated by Vincent MEMBRÉ about 11 years ago
- Target version changed from 2.9.0~rc1 to 2.9.0~rc2
This won't be done for beta1
Updated by Vincent MEMBRÉ about 11 years ago
- Target version changed from 2.9.0~rc2 to 2.9.0
Delayed to 2.9 finale release
Updated by Nicolas CHARLES almost 11 years ago
I do agree that this value is too big currently !
Updated by François ARMAND almost 11 years ago
- Status changed from New to 8
It was validated with JCL that:
- we need to have the reports for a long period, so that we can do post mortem analysis / plug reporting module even without notification period (and so we need to have a big time for the archived reports database)
- but there is no need for a long retention period for the main database.
So, let's go for 2 days only for the main database.
Updated by François ARMAND almost 11 years ago
- Status changed from 8 to 13
- Assignee set to Vincent MEMBRÉ
Updated by Jonathan CLARKE almost 11 years ago
I would prefer 3 days so that one can still see Fridays reports on a Monday morning.
Updated by Anonymous almost 11 years ago
- Status changed from 13 to Pending release
Applied in changeset 76e729a31d424b5ab6021771883fdc271dbb9538.
Updated by Vincent MEMBRÉ almost 11 years ago
- Subject changed from Change default values for Execution Report retention times to Reduce default maximum days of reports retained
Updated by Matthieu CERDA almost 11 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.9.0, which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2013-December/000067.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog29
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/