Search Index Management Commands Fail To Detect Collection on Other Shards

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.1.0-rc0, 7.0.3
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • ALL
    • v7.0
    • Execution EMEA Team 2023-08-07
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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 

            Assignee:
            Jordi Olivares Provencio
            Reporter:
            Evan Plotkin
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: