Project

General

Profile

Actions

Bug #15021

open

When receiving lots of reports, while load is high, an error occurs on node compliance historisation

Added by Nicolas CHARLES over 4 years ago. Updated about 1 year ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Performance and scalability
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
27
Regression:

Description

[2019-06-04 17:16:19] ERROR report - Error when saving node compliances: Batch entry 10 insert into nodecompliance (nodeid, runtimestamp, endoflife, runanalysis, summary, details)
 values ('284a4640-53eb-4ee1-a4b4-cb7ee4a42aee', '2019-06-04 17:12:55+00', '2019-06-04 17...
[2019-06-04 17:16:19] WARN  explain_compliance.be22c24e-221e-49a3-be66-842a50ab6809 - Received a run at 2019-06-04T17:12:26.000Z for node 'be22c24e-221e-49a3-be66-842a50ab6809' with configId '20190603-103341-2adab15d' but that node should be sending reports for configId 20190604-162615-8929003b


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #10478: Error on inserting into nodecompliance tableResolvedFrançois ARMANDActions
Actions #1

Updated by Vincent MEMBRÉ over 4 years ago

  • Subject changed from when pleinty of reports are recieved, and load is high, there's an error on node compliance historisation to When receiving lots of reports, while load is high, an error occurs on node compliance historisation
Actions #2

Updated by Nicolas CHARLES over 4 years ago

this seems related with full gc kicking in

Actions #3

Updated by Nicolas CHARLES over 4 years ago

it also seems to happen after this step of generation
INFO policy.generation - Configuration of following nodes were updated, their promises are going to be written:

Actions #4

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.12 to 5.0.13
Actions #5

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.13 to 5.0.14
Actions #6

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 5.0.14 to 5.0.15
Actions #7

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 5.0.15 to 5.0.16
Actions #8

Updated by Alexis Mousset over 3 years ago

  • Target version changed from 5.0.16 to 5.0.17
Actions #9

Updated by François ARMAND over 3 years ago

  • Related to Bug #10478: Error on inserting into nodecompliance table added
Actions #10

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 5.0.17 to 5.0.18
Actions #11

Updated by François ARMAND about 3 years ago

  • Category changed from Web - Compliance & node report to Performance and scalability
  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 27
Actions #12

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 5.0.18 to 5.0.19
Actions #13

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 5.0.19 to 5.0.20
Actions #14

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 5.0.20 to 797
Actions #15

Updated by Benoît PECCATTE about 2 years ago

  • Target version changed from 797 to 6.1.14
Actions #16

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions #17

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions #18

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions #19

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions #20

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions #21

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 6.1.19 to 6.1.20
Actions #22

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 6.1.20 to 6.1.21
Actions #23

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 6.1.21 to old 6.1 issues to relocate
Actions

Also available in: Atom PDF