Project

General

Profile

Bug #10168

Deadlock with simultaneous generation and new reports

Added by François ARMAND 7 months ago. Updated 7 months ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
Target version (plugin):
Severity:
User visibility:
Effort required:
Priority:

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.

Associated revisions

Revision 47bdd2d4
Added by François ARMAND 7 months ago

Fixes #10168: Deadlock with simultaneous generation and new reports

History

#1 Updated by François ARMAND 7 months 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

#2 Updated by François ARMAND 7 months ago

  • Description updated (diff)

#3 Updated by François ARMAND 7 months ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

#4 Updated by Vincent MEMBRÉ 7 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.1.18, 3.2.11, 4.0.3 and 4.1.0~beta3 which were released today.

Also available in: Atom PDF