Actions
Bug #10168
closed
Deadlock with simultaneous generation and new reports
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
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.
Updated by François ARMAND about 7 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/1488
Updated by François ARMAND about 7 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder|47bdd2d4b70eb5832b9b9b88ad5d237983c14512.
Updated by Vincent MEMBRÉ about 7 years ago
- Status changed from Pending release to Released
Actions