Actions
Bug #23699
closed
Event log migration takes too long
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No
Description
In #19317, we added a migration check that update event log table on start up. but this blocks on big setups with a huge amount of event logs and jetty is killed because it takes too long to start
Updated by Vincent MEMBRÉ about 1 year ago
- Related to Bug #19317: Last modified attribute of change request is always "unknown" added
Updated by Vincent MEMBRÉ about 1 year ago
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
Updated by Vincent MEMBRÉ about 1 year ago
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/5160
Updated by Anonymous about 1 year ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|6748fccb9e162b3e469c813ca38efdeaee66a542.
Updated by Elaad FURREEDAN about 1 year ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ about 1 year ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.3.9 and 8.0.2 which were released today.
Updated by Clark ANDRIANASOLO 12 months ago
- Related to Bug #23836: Event log migration should not be done every time added
Actions