Actions
Bug #4091
closed
When we migrate to 2.8, the time to catch up on all the nodes execution time is very long
Status:
Released
Priority:
2
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
When upgrading to 2.8 with already data in the database, the time for the Agent Execution Service to catch up with all execution can be up to 1 hours, preventing the web app from displaying the reports information during this time
We should improve the migration script to gather all information immediatly (clever use of SQL query + temp table give about 1 minutes for the result)
Updated by Nicolas CHARLES about 11 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/352
With this, I go from about 40 minutes to about 1 minute to gather all the data
Updated by Nicolas CHARLES about 11 years ago
Updated by Nicolas CHARLES about 11 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset 4b91a6ac26f583eaabb9990c1fb48cd8481828c7.
Updated by Anonymous about 11 years ago
Applied in changeset 3a8f5db30d401d65885ce6b81e0d40fdd9d057d8.
Updated by Vincent MEMBRÉ about 11 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.8.0~rc1, which was released on Friday 25/10/2013.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2013-October/000057.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog28
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Actions