Bug #3471
closed
When archiving is processing, Rudder sees the Archived events table size but not the last/first event date in it
Added by Matthieu CERDA over 11 years ago.
Updated over 11 years ago.
Category:
Web - Maintenance
Description
Rudder sees the Archived events table size but not the last/first event date in it !
See the enclosed screeshot.
This is confusing :)
(A bit of background: This has been seen after a manual archiving)
Files
- Description updated (diff)
- Status changed from New to Discussion
- Assignee changed from François ARMAND to Matthieu CERDA
Is the archiver idle ?
It can't get the oldest/newest while the archiving is not over.
Ok I just saw your description update, so the archiving was over... quite strange then, I'll look into this
- Target version changed from 2.5.2 to 2.5.3
- Status changed from Discussion to In progress
- Assignee changed from Matthieu CERDA to François ARMAND
- Subject changed from Rudder sees the Archived events table size but not the last/first event date in it to When archiving is processing, Rudder sees the Archived events table size but not the last/first event date in it
So, I can't reproduce it with smal report database, but with big database, we see some latency during which data are inconsistent.
So, it is likelly that until archiving are over, Postgres return what it can, and most of it is just barelly right.
So, we should add a warning message saying "be careful, archiving is processing, data may not be up to date".
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/190
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Status changed from Pending release to Released
Also available in: Atom
PDF
Updated by Matthieu CERDA 
Updated by 
Updated by Nicolas PERRON 
Updated by 