Actions
Bug #6207
closedDeleting a directive is VERY slow
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
Even in the most simple case (a directive not used anywhere, on a fresh Rudder install), deleting a directive takes several seconds.
Code hint: the cause is that along the deleting, we get the directive from LDAP (with a lock), then get the the active directive (with a lock for the same think), then need to wait until the exaustion algo of the locking system sort things out. This is, of course. BAD BAD BAD BAD.
Updated by Vincent MEMBRÉ almost 10 years ago
- Target version changed from 2.10.9 to 2.10.10
Updated by François ARMAND almost 10 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Target version deleted (
2.10.10) - Pull Request set to https://github.com/Normation/rudder/pull/808
Updated by François ARMAND almost 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset 1bf661c12d00e5b09701ecf002093133ef38ccb4.
Updated by Vincent MEMBRÉ almost 10 years ago
Applied in changeset 6e56daa7af62a4245b8e99d028a8dd1d4b863293.
Updated by Vincent MEMBRÉ over 9 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.10.10 and 2.11.7, which were released on 05/02/2015.
- Announcement 2.10 2.11
- Changelog 2.10 2.11
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Actions