Actions
Bug #15021
closed
When receiving lots of reports, while load is high, an error occurs on node compliance historisation
Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
No
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
Updated by 
Updated by 
Updated by 
Updated by 
Updated by
Actions