Bug 2164725

Summary:	Healthcheck tool should warn admin about creating a substring index on membership attribute
Product:	Red Hat Directory Server	Reporter:	thierry bordaz <tbordaz>
Component:	389-ds-base	Assignee:	LDAP Maintainers <idm-ds-dev-bugs>
Status:	CLOSED MIGRATED	QA Contact:	LDAP QA Team <idm-ds-qe-bugs>
Severity:	high	Docs Contact:	Evgenia Martynyuk <emartyny>
Priority:	high
Version:	12.1	CC:	emartyny, idm-ds-dev-bugs, mreynolds, pasik
Target Milestone:	DS13.0	Keywords:	Triaged
Target Release:	dirsrv-13.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	sync-to-jira
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-26 13:48:37 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 thierry bordaz 2023-01-26 09:54:04 UTC

Description of problem:
An entry containing membership attribute is usually a group and the attribute may contains many values.
When changing the valueset, substring index is very expensive even for a minor change like deleting a single value.

When adding such index type, the administrator should be warn of the cost and double check that the index is required. 

Version-Release number of selected component (if applicable):


How reproducible:
See https://bugzilla.redhat.com/show_bug.cgi?id=1868348 and the discussion in the related jira ticket Actual results:


Expected results:
Warn the admin of possible high cost of substing index on membership attributes


Additional info:

Comment 1 thierry bordaz 2023-01-26 10:00:13 UTC

To clarify this BZ is to improve healthcheck diagnostic on an already deployed instance

Comment 3 Viktor Ashirov 2024-06-26 13:48:37 UTC

This BZ has been automatically migrated to Red Hat Issue Tracker https://issues.redhat.com/browse/DIRSRV-10. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.