Project

General

Profile

Actions

Bug #18983

closed

A writeLock must never be in a read lock for LDAP repo

Added by François ARMAND about 3 years ago. Updated about 3 years ago.

Status:
Released
Priority:
N/A
Category:
Performance and scalability
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:

Description

In Ldap repos, we have at several places lock.readLock.use(... get ldap info... lock.writeLock.use(modify ldap))

This is broken: we could have two concurrent read, then a write which modify what should have been read by the other fiber.


Related issues 5 (0 open5 closed)

Related to Rudder - Bug #18584: semaphore gurading LDAP repos are created each timeReleasedVincent MEMBRÉActions
Related to Rudder - Bug #16441: Git error at install on debian9RejectedActions
Related to Rudder - Bug #19398: Git error when deleting a node or archiving everything, and very slow gitResolvedNicolas CHARLESActions
Has duplicate Rudder - Bug #15020: Lock access error on git when writing thousands of files during a policy generation ResolvedActions
Has duplicate Rudder - Bug #18892: Technique Upgrade failed with a JGit error after upgrading from 5.0.20 to 6.1.9ResolvedActions
Actions #1

Updated by François ARMAND about 3 years ago

  • Related to Bug #18584: semaphore gurading LDAP repos are created each time added
Actions #2

Updated by François ARMAND about 3 years ago

  • Status changed from New to In progress
Actions #3

Updated by François ARMAND about 3 years ago

  • Target version changed from 798 to 6.1.10
Actions #4

Updated by François ARMAND about 3 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/3527
Actions #5

Updated by François ARMAND about 3 years ago

  • Has duplicate Bug #15020: Lock access error on git when writing thousands of files during a policy generation added
Actions #6

Updated by François ARMAND about 3 years ago

  • Has duplicate Bug #18892: Technique Upgrade failed with a JGit error after upgrading from 5.0.20 to 6.1.9 added
Actions #7

Updated by François ARMAND about 3 years ago

  • Status changed from Pending technical review to Pending release
Actions #8

Updated by François ARMAND about 3 years ago

  • Fix check changed from To do to Checked
Actions #9

Updated by Vincent MEMBRÉ about 3 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 6.1.10 and 6.2.3 which were released today.

Actions #10

Updated by François ARMAND about 3 years ago

  • Related to Bug #16441: Git error at install on debian9 added
Actions #11

Updated by François ARMAND over 2 years ago

  • Related to Bug #19398: Git error when deleting a node or archiving everything, and very slow git added
Actions

Also available in: Atom PDF