Project

General

Profile

Actions
Copy link

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 about 11 years ago. Updated almost 11 years ago.

Status:
Released
Priority:
2
Assignee:
Vincent MEMBRÉ
Category:
Web - Maintenance
Target version:
2.5.3
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

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

wtf2.png (30.3 KB) wtf2.png Matthieu CERDA, 2013-04-16 12:33
Actions
Copy link
 #1

Updated by Matthieu CERDA about 11 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ about 11 years ago

  • 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.

Actions
Copy link
 #3

Updated by Vincent MEMBRÉ about 11 years ago

Ok I just saw your description update, so the archiving was over... quite strange then, I'll look into this

Actions
Copy link
 #4

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.5.2 to 2.5.3
Actions
Copy link
 #5

Updated by François ARMAND about 11 years ago

  • Status changed from Discussion to In progress
  • Assignee changed from Matthieu CERDA to François ARMAND
Actions
Copy link
 #6

Updated by François ARMAND about 11 years ago

  • 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".

Actions
Copy link
 #7

Updated by François ARMAND about 11 years ago

  • 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
Actions
Copy link
 #8

Updated by François ARMAND about 11 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #10

Updated by Nicolas PERRON almost 11 years ago

  • Status changed from Pending release to Released
Actions
Copy link

Also available in: Atom PDF