Project

General

Profile

Actions

Bug #14080

closed

Huge latency between inventory sent and inventory appears in Rudder

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

Status:
Released
Priority:
N/A
Category:
Web - Nodes & inventories
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
First impressions of Rudder
Effort required:
Small
Priority:
96
Name check:
Fix check:
Regression:

Description

There is a huge latency between the moment someone run "rudder agent inventory" on a node and the moment the corresponding node appears in new nodes.

This is due to the need for rudder agent to run on the root server, which can take up to 5 minutes.

Every and all Rudder users hate that behavior. There is a workaround with a perl file watcher that removes that latency (see: https://github.com/Normation/rudder-tools/tree/master/contrib/rudder-inventory-daemon) but it is not native to Rudder, so the user first experience is still poor.

So, we need to add the file watcher directly into Rudder. By doing that, we also remove the need to send inventories by HTTP from localhost to localhost...

We still need to keep the old REST API, because file watchers are not very robust and so we have rudder agent to keep missed inventories.
We also need to be able to not use the file watcher (by configuration file), and to control it (start/stop/restart) by API.


Subtasks 2 (0 open2 closed)

Bug #14095: Compilation error in ldap-inventoryReleasedFrançois ARMANDActions
Bug #14097: Migration script to add default watch values in inventory-web.propertiesReleasedVincent MEMBRÉActions

Related issues 2 (0 open2 closed)

Related to Rudder - Bug #14237: Inventory watcher is too quick and does not wait for file closeReleasedNicolas CHARLESActions
Related to Rudder - User story #11248: Rudder must process inventories from unaccepted nodes immediatellyRejectedActions
Actions

Also available in: Atom PDF