Project

General

Profile

Actions

Bug #7020

closed

Copy ncf only if it is updated

Added by Nicolas CHARLES over 9 years ago. Updated over 9 years ago.

Status:
Released
Priority:
1 (highest)
Category:
Performance and scalability
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

When we copy ncf on the nodes, we use a very naive method of checking every files, which uses network ressources and CPU

The solution to be used is to make at every run a hash of ncf, and compare the hash of ncf with what we have on the node. If they differ, then we copy the promise
The risk there is that promise were regenerated, but hash not yet computed, so in this case, we'll copy ncf if promises has been updated

Note: the relay will always check for update of ncf, to prevent delays that may arise between hash update and real update


Related issues 2 (0 open2 closed)

Related to Rudder - Bug #5459: Tools directory is not always correctly updated on nodesReleasedJonathan CLARKE2014-09-01Actions
Related to Rudder - Bug #7473: ncf copy is always repaired on server due to an non-convergent hash functionReleasedBenoît PECCATTE2015-11-25Actions
Actions

Also available in: Atom PDF