Actions
Bug #7987
closedrudder-upgrade takes too long
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
The pgsql query
select count(*) from (select xpath('/entry/*[@fileFormat=<?>]',data) AS x from eventlog) as Y where array_upper(x, 1) > 0takes too long if you have 300k+ entries.
Server: SLES11 SP3 // postgresql91-server-9.1.18-0.3.1
This is also heavily impacted by the fact, that the script /opt/rudder/bin/rudder-upgrade, that contains this statement, is run twice on a single-server installation:
A 3.0.11->3.0.13 update took:
rpm rudder-inventory-ldap: 61 minutes rpm rudder-webapp: 61 minutesThis could been solved if you would:
- Save each type of update that is not required, because it has been checked during any previous update.
- Execute this kind of maintenance by the jetty in an async job, not during the RPM installation.
Actions