Node configuration cache is invalidated too often
There a bug in the current "save node configuration cache" method that delete node cache for not modified cache. So, in some case, you could hit cycle where a part of nodes are saved (removing the other part), then the other part is saved (removing the first), etc.
Of course, all forseable bad consequences happens: increased generation time, patological config id modification without actual changes in the expected reports (and yes, we get bad results with compliance), etc.
Updated by Vincent MEMBRÉ over 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.21, 3.0.16, 3.1.10 and 3.2.3 which were released on 2016-06-01, but not announced.
- 2.11: Changelog
- 3.0: Changelog
- 3.1: Changelog
- 3.2: Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/