[SERVER-82437] db.collection.getSearchIndexes(<indexName>) returns duplicate index Created: 25/Oct/23  Updated: 04/Jan/24  Resolved: 05/Dec/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.2.1, 7.3.0-rc0, 7.0.5, 6.0.13

Type: Bug Priority: Major - P3
Reporter: Fiona Chang Assignee: Gil Alon
Resolution: Fixed Votes: 0
Labels: greenerbuild
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by COMPASS-7505 Investigate changes in SERVER-82437: ... Closed
Related
related to SERVER-82945 Increase sharded search / vectorSearc... Backlog
Assigned Teams:
Query Integration
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.2, v7.0, v6.0
Sprint: QI 2023-12-11
Participants:

 Comments   
Comment by Max Hirschhorn [ 08/Nov/23 ]

My general question about the $listSearchIndexes aggregation stage is why does mongos broadcast at all? Mongos is also spawned with --searchIndexManagementHostAndPort and so it seems like it could handle the aggregation request directly. Mongos handling the command request itself without forwarding to a shard is how the listSearchIndexes command was implemented.

Comment by Fiona Chang [ 25/Oct/23 ]

db.collection.getSearchIndexes(<indexName>) returns duplicate index when data are on all sharded collection

Generated at Thu Feb 08 06:49:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.