Project

General

Profile

Actions
Copy link

Bug #3917

closed

Archiving reports should not break on on duplicate IDs or key

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

Status:
Rejected
Priority:
2
Assignee:
Nicolas CHARLES
Category:
Web - Compliance & node report
Target version:
3.1.19
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

When Rudder automatically archives reports, it does it in 3 step:
  1. copy from ruddersysevents to archivedreports
  2. delete from ruddersysevents
  3. vaccumm

If the webapp is stopped between 1 and 2, we have the archive in an invalid state, causing it to fail later as it tries to insert already existing entries into the archivedruddersysevents.

In fact, we want to be able to have the archived execution reports on an other DB, so we don't want to add transaction, but be smart about how we handle already migrated reports.

Related issues 1 (0 open — 1 closed)

Is duplicate of Rudder - Bug #10171: If the Rudder Web Interface is interrupted during the second step of reports archiving, then it won't never succeed in archiving againReleasedFrançois ARMANDActions
Actions
Copy link
 #1

Updated by François ARMAND about 11 years ago

  • Subject changed from The reports archive are not transactionnal to Archiving reports should not break on on duplicate IDs or key
  • Description updated (diff)
Actions
Copy link
 #2

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.6.6 to 2.4.10
Actions
Copy link
 #3

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.4.10 to 2.6.7
Actions
Copy link
 #4

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.6.7 to 2.6.8
Actions
Copy link
 #5

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.6.8 to 2.6.9
Actions
Copy link
 #6

Updated by Nicolas PERRON about 11 years ago

  • Priority changed from N/A to 2
  • Target version changed from 2.6.9 to 2.6.10

It seems important.

Actions
Copy link
 #7

Updated by Vincent MEMBRÉ almost 11 years ago

  • Target version changed from 2.6.10 to 2.6.11
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ over 10 years ago

  • Target version changed from 2.6.11 to 2.6.12
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ over 10 years ago

  • Target version changed from 2.6.12 to 2.6.13
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ over 10 years ago

  • Target version changed from 2.6.13 to 2.6.14
Actions
Copy link
 #11

Updated by Jonathan CLARKE over 10 years ago

  • Target version changed from 2.6.14 to 2.6.16
Actions
Copy link
 #12

Updated by Jonathan CLARKE over 10 years ago

  • Target version changed from 2.6.16 to 2.6.17
Actions
Copy link
 #13

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.6.17 to 2.6.18
Actions
Copy link
 #14

Updated by Matthieu CERDA about 10 years ago

  • Target version changed from 2.6.18 to 2.6.19
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.6.19 to 2.6.20
Actions
Copy link
 #16

Updated by François ARMAND almost 10 years ago

  • Assignee set to Nicolas CHARLES
  • Target version changed from 2.6.20 to 2.10.10

Nico, I think it's not more the case in 2.10. Could you confirm, and if so closed the ticket ?

Actions
Copy link
 #17

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.10.10 to 2.10.11
Actions
Copy link
 #18

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.11 to 2.10.12
Actions
Copy link
 #19

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.12 to 2.10.13
Actions
Copy link
 #20

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.13 to 2.10.14
Actions
Copy link
 #21

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.14 to 2.10.15
Actions
Copy link
 #22

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.15 to 2.10.16
Actions
Copy link
 #23

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.16 to 2.10.17
Actions
Copy link
 #24

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.17 to 2.10.18
Actions
Copy link
 #25

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.18 to 2.10.19
Actions
Copy link
 #26

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.19 to 2.10.20
Actions
Copy link
 #27

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.10.20 to 2.11.18
Actions
Copy link
 #28

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.11.18 to 2.11.19
Actions
Copy link
 #29

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.19 to 2.11.20
Actions
Copy link
 #30

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.20 to 2.11.21
Actions
Copy link
 #31

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.21 to 2.11.22
Actions
Copy link
 #32

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.22 to 2.11.23
Actions
Copy link
 #33

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.11.23 to 2.11.24
Actions
Copy link
 #34

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.24 to 308
Actions
Copy link
 #35

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 308 to 3.1.14
Actions
Copy link
 #36

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions
Copy link
 #37

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions
Copy link
 #38

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions
Copy link
 #39

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions
Copy link
 #40

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions
Copy link
 #41

Updated by François ARMAND over 7 years ago

  • Has duplicate Bug #10171: If the Rudder Web Interface is interrupted during the second step of reports archiving, then it won't never succeed in archiving again added
Actions
Copy link
 #42

Updated by François ARMAND over 7 years ago

  • Has duplicate deleted (Bug #10171: If the Rudder Web Interface is interrupted during the second step of reports archiving, then it won't never succeed in archiving again)
Actions
Copy link
 #43

Updated by François ARMAND over 7 years ago

  • Is duplicate of Bug #10171: If the Rudder Web Interface is interrupted during the second step of reports archiving, then it won't never succeed in archiving again added
Actions
Copy link
 #44

Updated by François ARMAND over 7 years ago

  • Status changed from New to Rejected

This was corrected in #10171

Actions
Copy link

Also available in: Atom PDF