Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2151526

Summary:	RFE Syncing indexes within a replicated cluster
Product:	Red Hat Directory Server	Reporter:	Eddy Resnick <eresnick>
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:	11.4	CC:	ekeck, emartyny, idm-ds-dev-bugs, mreynolds, musoni, progier, tbordaz, vashirov
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	Linux
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:19 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 Eddy Resnick 2022-12-07 13:09:12 UTC

Description of problem:
Indexes within a replication cluster should have an option to be synchronized to keep consistency of the cluster

Version-Release number of selected component (if applicable):
RHEL 11 (389-Directory/1.4.3.29 B2022.087.1507)


How reproducible:
N/A


Steps to Reproduce:
N/A

Actual results:
Indexes can be different on nodes in the cluster


Expected results:
Suggested feature to propagate indexes from one supplier to the rest of the servers in the replication cluster.
The feature should allow for:
- a cluster wide overwrite from one source
- a wholesale merge of indexes from one source to the other servers
- an optional list of indexes to be propagated with either overwrite or merge as the final outcome

Additional info:

Customer case #03387904

Comment 7 Viktor Ashirov 2024-06-26 13:48:19 UTC

This BZ has been automatically migrated to Red Hat Issue Tracker https://issues.redhat.com/browse/DIRSRV-19. 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.