Project

General

Profile

Actions

Bug #8427

closed

Parallel traversal of new promises directories causes some nodes promises to not be updated

Added by François ARMAND almost 8 years ago. Updated almost 8 years ago.

Status:
Released
Priority:
1
Category:
Web - Compliance & node report
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

When we generate new promises, we do that in a parallel way for each node, so that I/O latency on one node is not making all of the other waits.

The code is not correctly synchronized, and so we loose in the process the list of nodes that were processed. The result is that new nodes may not have the "rules.new" directory moved to "rules", and keep getting old promises.

It's the same problem as: http://www.rudder-project.org/redmine/issues/7403


Related issues 1 (0 open1 closed)

Related to Rudder - Architecture #7403: Paralell sequence may have a not correct result (missing elements)ReleasedFrançois ARMAND2015-11-13Actions
Actions

Also available in: Atom PDF