[SERVER-48423] Initial sync should ignore multiple text indexes on same collection error Created: 26/May/20  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Suganthi Mani Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: former-quick-wins
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
related to SERVER-32225 Initial sync should ignore multiple t... Closed
is related to SERVER-48457 Revert ignoring multiple text indexes... Closed
Assigned Teams:
Replication
Operating System: ALL
Backport Requested:
v4.4
Participants:
Linked BF Score: 0

 Description   

After SERVER-32225, users will be able to create multiple text indexes on a single collection. SERVER-32225 actually relaxes the constraint only for system (internal) connections but the rule "one text index per collection" applies to user connections. When the user tries to create indexes on a primary, the actual index building part , spec creation & spec validity check are done by the internal (system) worker thread "IndexBuildsCoordinatorMongod" and not by the parent(user) thread. So, technically a user connection will be able to create multiple text indexes. 

EDIT: This ticket will be repurposed to fix the issue mentioned in SERVER-32225.


Generated at Thu Feb 08 05:17:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.