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

Also available in: Atom PDF