Project

General

Profile

Actions
Copy link

Bug #10168

closed

Deadlock with simultaneous generation and new reports

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

Status:
Released
Priority:
N/A
Assignee:
Nicolas CHARLES
Category:
Web - Config management
Target version:
3.1.18
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

We observed a case where a generation can't end.

It seems to be link to the call of "cachedCompliance.invalidate(updatedNodeIds)", which is synchronized.
I'm not sure why it can terminate during a generation - in fact, maybe it is not a dead lock, and invalidate is just very, very long. But there is no reason the whole generation is blocked by that.

Actions
Copy link

Also available in: Atom PDF