[SERVER-78847] Search Index Management Commands Fail To Detect Collection on Other Shards Created: 10/Jul/23  Updated: 29/Oct/23  Resolved: 01/Aug/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, 7.0.3

Type: Bug Priority: Major - P3
Reporter: Evan Plotkin Assignee: Jordi Olivares Provencio
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
backported by SERVER-80988 [6.0] Search Index Management Command... Closed
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.0
Sprint: Execution EMEA Team 2023-08-07
Participants:

 Description   

On a sharded cluster, there are issues with commands being rejected because the collection was not found.  It looks like maybe it is not properly checking the existence of the collection on other shards?

Atlas [mongos] newDB> db.test.insertOne({"a":"b"})
{
acknowledged: true,
insertedId: ObjectId("64ac7f01a79de8670d490112")
}
Atlas [mongos] newDB> db.test.createSearchIndex({"name":"default","definition":{"mappings":
{"dynamic":"true"}
}})
MongoServerError: collection newDB.test not found 


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