Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-76624

Server can falsely report CollectionUUIDMismatch

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Catalog and Routing
    • ALL
    • Execution NAMR Team 2023-07-10, Sharding EMEA 2023-07-24, Sharding EMEA 2023-08-07, Sharding EMEA 2023-08-21, Sharding EMEA 2023-09-04, Sharding EMEA 2023-09-18, Sharding EMEA 2023-10-02, Sharding EMEA 2023-10-16, Sharding EMEA 2023-10-30, CAR Team 2023-11-13, CAR Team 2023-11-27, CAR Team 2023-12-11, CAR Team 2023-12-25, CAR Team 2024-01-08, CAR Team 2024-02-05
    • 2

    Description

      In a mongosync test run, mongod mistakenly reported a collectionUUIDMismatch error. The sequence of events was:

      • mongosync creates a collection, testDB.userWriteBlockColl
      • mongod successfully does so, and gives it the UUID 3ca88158-8e77-49fb-9fcd-1bff14d26f5f
      • mongosync runs the following command, with that UUID, and gets a collectionUUIDMismatch error

       

       {
        "aggregate": "userWriteBlockColl",
        "collectionUUID": { "$uuid": "3ca88158-8e77-49fb-9fcd-1bff14d26f5f" },
        "pipeline": [
          { "$listCatalog": {} },
          { "$addFields": { "collectionUUID": "$md.options.uuid" } },
          { "$addFields": { "ns": "$md.ns" } },
          { "$project": { "md.options.uuid": 0 } },
          { "$addFields": { "options": "$md.options" } }
        ],
        "cursor": {},
        "readConcern": {
          "afterClusterTime": {
            "$timestamp": { "t": 1682347099, "i": 21 }
          }
        },
      }

       

      The mongod returns this very confusing error, with the same UUID and the same collection name in both expected and actual collection:

      {
          db:                 "testDB", 
          collectionUUID:     UUID("3ca88158-8e77-49fb-9fcd-1bff14d26f5f"), 
          expectedCollection: "userWriteBlockColl", 
          actualCollection:   "userWriteBlockColl" 
      } 

       

      I collected some of the relevant logs in this GitHub gist, but the full mongod logs are available from the Evergreen task page for the failed mongosync tests.

      Attachments

        Activity

          People

            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            michael.mcclimon@mongodb.com Michael McClimon
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: