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
Internal unindexed searches in syncrepl #4443
Comments
Are they indexed for equality? "eq" Can you provide the index entries from dse.ldif please? As I recall IPA used to use an invalid format for the index types (I'm sure that's been corrected, but I'd like to confirm it). Do you see the index files under /var/lib/dirsrv/slapd-INST/db/changelog/ ? If not, please "reindex" those indexes... |
and
|
Does dbscan return anything?
|
Yes, it does. The values, of course, are different to what is in the original report as this is different system but nevertheless, it is working FreeIPA deployment:
|
Thanks for checking! I'm assuming this system is also generating those error messages? Anyway I was really hoping it was a config/timing issue :-) We'll look into this soon... |
@mreynolds389 It could be that there is an internal filter transform that is occuring that has an un-indexed filter component we aren't logging. |
Bug Description: When a non-system index is added to a backend it is disabled until the database is initialized or reindexed. So in the case of the retro changelog the changenumber index is alway disabled by default since it is never initialized. This leads to unexpected unindexed searches of the retro changelog. Fix Description: If an index has "nsSystemIndex" set to "true" then enable it immediately. relates: 389ds#4443 Reviewed by: spichugi & tbordaz(Thanks!!)
Bug Description: When a non-system index is added to a backend it is disabled until the database is initialized or reindexed. So in the case of the retro changelog the changenumber index is alway disabled by default since it is never initialized. This leads to unexpected unindexed searches of the retro changelog. Fix Description: If an index has "nsSystemIndex" set to "true" then enable it immediately. relates: #4443 Reviewed by: spichugi & tbordaz(Thanks!!)
Bug Description: When a non-system index is added to a backend it is disabled until the database is initialized or reindexed. So in the case of the retro changelog the changenumber index is alway disabled by default since it is never initialized. This leads to unexpected unindexed searches of the retro changelog. Fix Description: If an index has "nsSystemIndex" set to "true" then enable it immediately. relates: #4443 Reviewed by: spichugi & tbordaz(Thanks!!)
Bug Description: When a non-system index is added to a backend it is disabled until the database is initialized or reindexed. So in the case of the retro changelog the changenumber index is alway disabled by default since it is never initialized. This leads to unexpected unindexed searches of the retro changelog. Fix Description: If an index has "nsSystemIndex" set to "true" then enable it immediately. relates: #4443 Reviewed by: spichugi & tbordaz(Thanks!!)
Bug Description: When a non-system index is added to a backend it is disabled until the database is initialized or reindexed. So in the case of the retro changelog the changenumber index is alway disabled by default since it is never initialized. This leads to unexpected unindexed searches of the retro changelog. Fix Description: If an index has "nsSystemIndex" set to "true" then enable it immediately. relates: #4443 Reviewed by: spichugi & tbordaz(Thanks!!)
On latest Fedora Rawhide test composes I see plenty of complains about partial unindexed searches from syncrepl plugin even though there are indexes defined for the attributes specified in the filter:
Logs for the compose test: https://openqa.fedoraproject.org/tests/722674#downloads
Typical errors in the log:
If I'd look at the indexes for
cn=changelog
backend, the indexes for those two attributes are defined. Here is output from my local instance:The text was updated successfully, but these errors were encountered: