Actions
Bug #10171
closed
If the Rudder Web Interface is interrupted during the second step of reports archiving, then it won't never succeed in archiving again
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
Reports archiving happens by default every day.
It's a 3 steps procedure, with:
It's a 3 steps procedure, with:
- reports insertion into archivedruddersysevents from ruddersysevents
- deletion from ruddersysevents
- vaccuum
If this is interupted during step 2, then reports already moved will not be deleted, and on the following day they won't be archived (because of duplicate keys)
We should have a more robust system that would recover from where it stopped
(alternatives are to drop the unicity constraints on archivedruddersysevents, but this would lead to duplicate entries in this case)
Updated by Nicolas CHARLES almost 8 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES almost 8 years ago
Suggested implementation
- get A max id of archivedruddersysevents
- get R min id of ruddersysevents
- get C max id of ruddersysevents where date < archive date
- insert reports from [max(R,A) to C] to archivedruddersysevents
- delete reports smaller than C from ruddersysevents
Updated by Nicolas CHARLES almost 8 years ago
risk is: if insert into ruddersysevents is too long, and web interface is restarted, deletion never occurs, so we may add a delete in 3bis for all overlap
Updated by Nicolas CHARLES almost 8 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/1491
Updated by Nicolas CHARLES almost 8 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder|43cab768de9344e51d75e70fa1a5f5028a887099.
Updated by Vincent MEMBRÉ almost 8 years ago
- Status changed from Pending release to Released
Updated by François ARMAND over 7 years ago
- Is duplicate of Bug #3917: Archiving reports should not break on on duplicate IDs or key added
Updated by François ARMAND over 7 years ago
- Is duplicate of deleted (Bug #3917: Archiving reports should not break on on duplicate IDs or key)
Updated by François ARMAND over 7 years ago
- Has duplicate Bug #3917: Archiving reports should not break on on duplicate IDs or key added
Actions