Bug #15021: When receiving lots of reports, while load is high, an error occurs on node compliance historisation - Rudder - Issue Tracker

Actions

Copy link

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

Target version:

old 6.1 issues to relocate

Pull Request:

Severity:

Minor - inconvenience | misleading | easy workaround

UX impact:

User visibility:

Operational - other Techniques | Rudder settings | Plugins

Effort required:

Priority:

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 open — 1 closed)

Actions

Copy link

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

Copy link

Updated by Nicolas CHARLES over 4 years ago

this seems related with full gc kicking in

Actions

Copy link

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

Copy link

Updated by Vincent MEMBRÉ about 4 years ago

Target version changed from 5.0.12 to 5.0.13

Actions

Copy link

Updated by Vincent MEMBRÉ about 4 years ago

Target version changed from 5.0.13 to 5.0.14

Actions

Copy link

Updated by Vincent MEMBRÉ almost 4 years ago

Target version changed from 5.0.14 to 5.0.15

Actions

Copy link

Updated by Vincent MEMBRÉ almost 4 years ago

Target version changed from 5.0.15 to 5.0.16

Actions

Copy link

Updated by Alexis Mousset over 3 years ago

Target version changed from 5.0.16 to 5.0.17

Actions

Copy link

Updated by François ARMAND over 3 years ago

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

Actions

Copy link

#10

Updated by Vincent MEMBRÉ over 3 years ago

Target version changed from 5.0.17 to 5.0.18

Actions

Copy link

#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