Issue 6554 - During import of entries without nsUniqueId, a supplier … #6582
+11
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…generates duplicate nsUniqueId (LMDB only) Bug description: During an import the entry is prepared (schema, operational attributes, password encryption,...) before starting the update of the database and indexes. A step of the preparation is to assign a value to 'nsuniqueid' operational attribute. 'nsuniqueid' must be unique. In LMDB the preparation is done by multiple threads (workers). In such case the 'nsuniqueid' are generated in parallel and as it is time based several values can be duplicated. Fix description: To prevent that the routine dbmdb_import_generate_uniqueid should make sure to synchronize the workers. fixes: 389ds#6554 Reviewed by:
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…generates duplicate nsUniqueId (LMDB only)
Bug description:
During an import the entry is prepared (schema, operational
attributes, password encryption,...) before starting the
update of the database and indexes.
A step of the preparation is to assign a value to 'nsuniqueid'
operational attribute. 'nsuniqueid' must be unique.
In LMDB the preparation is done by multiple threads (workers).
In such case the 'nsuniqueid' are generated in parallel and
as it is time based several values can be duplicated.
Fix description:
To prevent that the routine dbmdb_import_generate_uniqueid
should make sure to synchronize the workers.
fixes: #6554
Reviewed by: