Project

General

Profile

Actions

Bug #26494

open

Inventory tables takes significant storage leading to QuotaExceededError with many nodes

Bug #26494: Inventory tables takes significant storage leading to QuotaExceededError with many nodes

Added by Clark ANDRIANASOLO about 1 year ago. Updated 19 days ago.

Status:
New
Priority:
2
Category:
Performance and scalability
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
It bothers me each time
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Priority:
79
Name check:
To do
Fix check:
To do
Regression:
No

Description

When using the technique editor, I could end-up not being able to edit drafts, and I receive an error notification with a QuotaExceededError in the details, suggesting that I'm out of storage in the browser.

This is likely due to accumulated data in localStorage : when consulting the node details page of a node for the first time, opening the page leads to several data added to the localstorage, corresponding to an empty state of the bios, processors, net, var, os, storages, process, logsGrid, fs, softUpdates, controllers, etc.
All data is added in batch, this is due to using the DataTables library and displaying all tables as soon as the page is rendered, even if the "Inventory" tab and specific table has not been clicked in the browser.

Proposed solution :
We should make this lazy, at least by rendering the table data with AJAX instead of rendering it on the server-side page : https://github.com/Normation/rudder/blob/branches/rudder/8.1/webapp/sources/rudder/rudder-web/src/main/scala/com/normation/rudder/web/services/DisplayNode.scala#L420.

We could also do storage optimization in https://github.com/Normation/rudder/blob/branches/rudder/8.1/webapp/sources/rudder/rudder-web/src/main/javascript/rudder/rudder-datatable.js#L2423, but it could lead to compatibility issues and duplication, especially if we want to migrate away from DataTables.

Workaround is to empty the localStorage : localStorage.clear() in the browser console.


Related issues 2 (1 open1 closed)

Related to Rudder - Bug #6157: Rudder stores too much or too big cookies, causing white page with HTTP status: 413: FULL head (branch 2.11)ReleasedFrançois ARMANDActions
Related to Rudder - Bug #28063: Node details tabs content should be loaded asynchronouslyNewClark ANDRIANASOLOActions

Updated by Clark ANDRIANASOLO about 1 year ago Actions #1

  • UX impact set to It bothers me each time
  • User visibility set to Getting started - demo | first install | Technique editor and level 1 Techniques
  • Priority changed from 0 to 62

Updated by Elaad FURREEDAN about 1 year ago Actions #2

  • Priority changed from 62 to 95

Updated by Clark ANDRIANASOLO about 1 year ago Actions #3

  • Related to Bug #6157: Rudder stores too much or too big cookies, causing white page with HTTP status: 413: FULL head (branch 2.11) added

Updated by Clark ANDRIANASOLO about 1 year ago Actions #4

  • Priority changed from N/A to To review
  • Priority changed from 95 to 62

Updated by Clark ANDRIANASOLO about 1 year ago Actions #5

  • Priority changed from 62 to 95

Updated by Nicolas CHARLES about 1 year ago Actions #7

  • Assignee set to Clark ANDRIANASOLO
  • Priority changed from To review to 2
  • Target version changed from 8.1.13 to 8.2.6

Updated by Nicolas CHARLES about 1 year ago Actions #8

  • Category changed from Web - Maintenance to Performance and scalability

Updated by Vincent MEMBRÉ 12 months ago Actions #9

  • Target version changed from 8.2.6 to 8.2.7
  • Priority changed from 95 to 93

Updated by Vincent MEMBRÉ 11 months ago Actions #10

  • Target version changed from 8.2.7 to 8.2.8
  • Priority changed from 93 to 92

Updated by Félix DALLIDET 9 months ago Actions #11

  • Target version changed from 8.2.8 to 8.2.9
  • Priority changed from 92 to 90

Updated by Vincent MEMBRÉ 7 months ago Actions #12

  • Target version changed from 8.2.9 to 1133
  • Priority changed from 90 to 87

Updated by Alexis Mousset 6 months ago Actions #13

  • Target version changed from 1133 to 8.3.6
  • Priority changed from 87 to 85

Updated by Vincent MEMBRÉ 5 months ago Actions #14

  • Target version changed from 8.3.6 to 8.3.7
  • Priority changed from 85 to 84

Updated by Vincent MEMBRÉ 4 months ago Actions #15

  • Target version changed from 8.3.7 to 8.3.8
  • Priority changed from 84 to 83

Updated by Vincent MEMBRÉ 4 months ago Actions #16

  • Target version changed from 8.3.8 to 8.3.9
  • Priority changed from 83 to 82

Updated by Clark ANDRIANASOLO 4 months ago Actions #17

  • Related to Bug #28063: Node details tabs content should be loaded asynchronously added

Updated by Vincent MEMBRÉ 2 months ago Actions #18

  • Target version changed from 8.3.9 to 8.3.10
  • Priority changed from 82 to 80

Updated by Vincent MEMBRÉ 19 days ago Actions #19

  • Target version changed from 8.3.10 to 8.3.11
  • Priority changed from 80 to 79
Actions

Also available in: PDF Atom