Project

General

Profile

Actions
Copy link

Bug #15020

closed

Lock access error on git when writing thousands of files during a policy generation

Added by Nicolas CHARLES over 5 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
Performance and scalability
Target version:
6.1.10
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
43
Name check:
Fix check:
Regression:

Description

the error is

[2019-06-04 16:18:34] ERROR com.normation.rudder.web.snippet.administration.Archives - Error when exporting groups, Directive library and Rules. <- Exception caught during execution of add command
[2019-06-04 16:18:34] ERROR com.normation.rudder.web.snippet.administration.Archives - org.eclipse.jgit.api.errors.JGitInternalException: Exception caught during execution of add command
org.eclipse.jgit.errors.LockFailedException: Cannot lock /var/rudder/configuration-repository/.git/index. Ensure that no other process has an open file handle on the lock file /var/rudder/configuration-repository/.git/index.lock, then you
 may delete the lock file and retry.

Related issues 1 (0 open — 1 closed)

Is duplicate of Rudder - Bug #18983: A writeLock must never be in a read lock for LDAP repoReleasedNicolas CHARLESActions
Actions
Copy link
 #1

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.12 to 5.0.13
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.13 to 5.0.14
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.14 to 5.0.15
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.15 to 5.0.16
Actions
Copy link
 #5

Updated by Alexis Mousset almost 5 years ago

  • Target version changed from 5.0.16 to 5.0.17
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
Actions
Copy link
 #7

Updated by François ARMAND over 4 years ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 27

If it goes away by itself with lower load, I would say it's minor. If it make rudder unable to scale past some point, it's major.

Actions
Copy link
 #8

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.18 to 5.0.19
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.19 to 5.0.20
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.20 to 797
Actions
Copy link
 #11

Updated by François ARMAND almost 4 years ago

  • Is duplicate of Bug #18983: A writeLock must never be in a read lock for LDAP repo added
Actions
Copy link
 #12

Updated by François ARMAND almost 4 years ago

  • Status changed from New to Resolved
  • Target version changed from 797 to 6.1.10

This is due to the fact that Jgit doesn't manage concurrency well, and if several write operation are concurrently done, we have cases where it breaks (but it's ~safe, since the presence of the .lock file prevent git repo corruption - but throws an exception).

The linked ticket #18983 should correct that, and a if not, we will need a fully sequential management of git operation with a git queue.

Actions
Copy link
 #13

Updated by François ARMAND over 3 years ago

  • Severity changed from Minor - inconvenience | misleading | easy workaround to Major - prevents use of part of Rudder | no simple workaround
  • Priority changed from 27 to 43
Actions
Copy link

Also available in: Atom PDF