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

Cluster checkMetadataConsistency fails with catalog shard

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.0.0-rc0, 7.1.0-rc0
    • None
    • None
    • None
    • Sharding NYC
    • Fully Compatible
    • ALL
    • v7.0
    • Sharding NYC 2023-04-17
    • 60

    Description

      The cluster version of the checkMetadataConsistency command will make a cursor on each shard and the config server, which get established together via establishCursors. That helper will send the same operationKey with every request, which must be unique per process, but when the config server is also a shard, we send the same operationKey to it twice, which fails the second command to arrive with BadValue.

      Attachments

        Activity

          People

            jack.mulrow@mongodb.com Jack Mulrow
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: