Project

General

Profile

Actions
Copy link

Bug #15609

closed

'Nodes Configurations' ldap entry is too big

Added by François ARMAND about 5 years ago. Updated about 5 years ago.

Status:
Released
Priority:
N/A
Assignee:
Nicolas CHARLES
Category:
Performance and scalability
Target version:
5.0.14
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
75
Name check:
Reviewed
Fix check:
Checked
Regression:

Description

When we have big installation, it fails to be written.

The problem is the 'nodeConfig' element, that we must keep semistructured so that we can analyse cache.
So we chose json, but it get really big.

The JSON is extremelly NOT optimized, and looks like that (for each node):

{
  "id": {
    "value": "0d396c08-2f18-4c38-ac1c-114f278357a3" 
  },
  "writtenDate": "2019-08-30T15:51:02.274Z",
  "nodeInfoHash": -1966720209,
  "parameterHash": -302045340,
  "nodeContextHash": 991614728,
  "policyHash": [
    {
      "draftId": {
        "ruleId": {
          "value": "57d2c204-5301-4ab6-8567-70afa3b6a126" 
        },
        "directiveId": {
          "value": "24185811-81d3-41e2-94c9-0b7cd1c43698" 
        },
        "techniqueVersion": {
          "epoch": 0,
          "upsreamTechniqueVersion": {
            "value": "1.0" 
          }
        }
      },
      "cacheValue": -1416633602
    },
    {
      "draftId": {
        "ruleId": {
          "value": "32377fd7-02fd-43d0-aab7-28460a91347b" 
        },
        "directiveId": {
          "value": "c6edb4df-c42b-4f7d-bde2-1befbe5ba8a4" 
        },
        "techniqueVersion": {
          "epoch": 0,
          "upsreamTechniqueVersion": {
            "value": "7.0" 
          }
        }
      },
      "cacheValue": 583482466
    },
 .... etc for each directive ....

Actions
Copy link

Also available in: Atom PDF