If I click on "Regenerate all policies", it clears the cache of changes, and slows down a lot the web interface
Performance and scalability
Minor - inconvenience | misleading | easy workaround
Infrequent - complex configurations | third party integrations
Clicking on "Regenerate all policies" clears all the caches, even the expensive changes cache (all changes made by the rules)
So it starts querying the database to get them over the last 3 days, and it can be very large, and slow to gather (with out of the box config, 2000 nodes and millions changes, it takes 4 minutes) - and it slows down everything
I don't see why Regenerating all policies would clear this cache.
As it is a (potentially big) behavior change, shouldn't it go to 4.1 ?
Maybe - it sounds more like a bug to me, but it changes indeed the behaviour
- User visibility set to Infrequent - complex configurations | third party integrations
- Status changed from New to In progress
- Assignee set to François ARMAND
So, it actually just call "clear cache" (the actual action from the button in setting). It does not seem trivial to change it to a pur "regenerate all". And perhaps it needs it own even log.
- Target version changed from 4.0.4 to 4.1.0
Ah, and so I would change it for 4.1, not 4.0.
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/1576
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
- Priority set to 0
This bug has been fixed in Rudder 4.1.0 which was released today.
Also available in: Atom