-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
db reindex corrupts RUV tombstone nsuniqueid index #4910
Milestone
Comments
mreynolds389
added a commit
to mreynolds389/389-ds-base
that referenced
this issue
Sep 9, 2021
Bug Description: During a reindex task we skip the RUV tombstone entry, which corrupts the nsuniqueid index. Fix Description: Make sure we still index nsuniqueid index for the RUV tombstone entry. relates: 389ds#4910 Reviewed by: firstyear & progier389 (Thanks!!)
mreynolds389
added a commit
that referenced
this issue
Sep 9, 2021
Bug Description: During a reindex task we skip the RUV tombstone entry, which corrupts the nsuniqueid index. Fix Description: Make sure we still index nsuniqueid index for the RUV tombstone entry. relates: #4910 Reviewed by: firstyear & progier389 (Thanks!!)
mreynolds389
added a commit
that referenced
this issue
Sep 9, 2021
Bug Description: During a reindex task we skip the RUV tombstone entry, which corrupts the nsuniqueid index. Fix Description: Make sure we still index nsuniqueid index for the RUV tombstone entry. relates: #4910 Reviewed by: firstyear & progier389 (Thanks!!)
mreynolds389
added a commit
that referenced
this issue
Sep 9, 2021
Bug Description: During a reindex task we skip the RUV tombstone entry, which corrupts the nsuniqueid index. Fix Description: Make sure we still index nsuniqueid index for the RUV tombstone entry. relates: #4910 Reviewed by: firstyear & progier389 (Thanks!!)
mreynolds389
added a commit
that referenced
this issue
Sep 9, 2021
Bug Description: During a reindex task we skip the RUV tombstone entry, which corrupts the nsuniqueid index. Fix Description: Make sure we still index nsuniqueid index for the RUV tombstone entry. relates: #4910 Reviewed by: firstyear & progier389 (Thanks!!)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
A regression was introduced some time ago where we incorrectly skip the RUV tombstone entry when it comes to reindexing. So after a reindex the nsuniqueid index does not contain the RUV entry, and any search using the DN in a "base" search will fail which in turn breaks replication.
The text was updated successfully, but these errors were encountered: