Project

General

Profile

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

Added by Nicolas CHARLES about 7 years ago. Updated about 7 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Maintenance
Target version:
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:
  1. reports insertion into archivedruddersysevents from ruddersysevents
  2. deletion from ruddersysevents
  3. 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)


Subtasks 1 (0 open1 closed)

Bug #10188: Spurious println introduced in parent ticketReleasedFrançois ARMANDActions

Related issues 1 (0 open1 closed)

Has duplicate Rudder - Bug #3917: Archiving reports should not break on on duplicate IDs or keyRejectedNicolas CHARLESActions
Actions

Also available in: Atom PDF