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 Vincent MEMBRÉ almost 5 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
Updated by Nicolas CHARLES almost 5 years ago
this seems related with full gc kicking in
Updated by Nicolas CHARLES almost 5 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:
Updated by Vincent MEMBRÉ almost 5 years ago
- Target version changed from 5.0.12 to 5.0.13
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 5.0.13 to 5.0.14
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 5.0.14 to 5.0.15
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 5.0.15 to 5.0.16
Updated by Alexis Mousset about 4 years ago
- Target version changed from 5.0.16 to 5.0.17
Updated by François ARMAND about 4 years ago
- Related to Bug #10478: Error on inserting into nodecompliance table added
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 5.0.17 to 5.0.18
Updated by François ARMAND almost 4 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
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 5.0.18 to 5.0.19
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 5.0.19 to 5.0.20
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 5.0.20 to 797
Updated by Benoît PECCATTE almost 3 years ago
- Target version changed from 797 to 6.1.14
Updated by Vincent MEMBRÉ almost 3 years ago
- Target version changed from 6.1.14 to 6.1.15
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.15 to 6.1.16
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.16 to 6.1.17
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.17 to 6.1.18
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.18 to 6.1.19
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 6.1.19 to 6.1.20
Updated by Vincent MEMBRÉ almost 2 years ago
- Target version changed from 6.1.20 to 6.1.21
Updated by Vincent MEMBRÉ almost 2 years ago
- Target version changed from 6.1.21 to old 6.1 issues to relocate
Updated by François ARMAND 5 months ago
- Status changed from New to Rejected
- Priority changed from 27 to 0
- Regression set to No
A lot of that code was changed since that time, and we didn't notice that error again. Since we were not able to reproduce it, I'm closing it.
Actions