Bug 2116948
Summary: | LMDB import is very slow | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | mreynolds |
Component: | 389-ds-base | Assignee: | Pierre Rogier <progier> |
Status: | CLOSED ERRATA | QA Contact: | LDAP QA Team <idm-ds-qe-bugs> |
Severity: | medium | Docs Contact: | Evgenia Martynyuk <emartyny> |
Priority: | high | ||
Version: | 9.1 | CC: | bsmejkal, emartyny, idm-ds-dev-bugs, pasik, tbordaz, vashirov |
Target Milestone: | rc | Keywords: | TestCaseProvided, Triaged |
Target Release: | 9.3 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | sync-to-jira | ||
Fixed In Version: | 389-ds-base-2.3.4-2.el9 | Doc Type: | Bug Fix |
Doc Text: |
.The LMDB import now works faster
Previously, to build the `entryrdn` index, LMDB import worker threads waited for other worker threads to ensure that the parent entry was processed. This generated lock contention that drastically slowed import. With this update, the LDIF import over LMDB database was redesigned and the provider thread stores the data about the entry RDN and its parents in a temporary database that the worker thread uses to build the `entryrdn` index. As a result, worker threads synchronization is no longer needed and the average import rate is better.
Note that the LMDB import still has an import rate three times slower than the BDB import because LMDB does not support concurrent write transactions.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2023-11-07 08:25:17 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
mreynolds
2022-08-09 15:16:54 UTC
Push upstream (only main) https://github.com/389ds/389-ds-base/issues/5408 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (389-ds-base bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:6350 |