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

metadataConsistencyCheck may be executed in a secondary RS node

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.1.0-rc0, 7.0.0-rc4
    • 7.0.0-rc3
    • None
    • None
    • Fully Compatible
    • ALL
    • v7.0
    • Sharding EMEA 2023-06-12
    • 146

    Description

      We must ensure that MetadataConsistencyCheck is executed only on a primary Replica Set node.

      When this is not happening?

      CASE 1

      • metadataConsistencyCheck command is received on node1
      • node1 steps down before we can set the opCtx as interruptible
      • metadataConsistencyCheck thread marks the opCtx as interruptible
      • metadataConsistencyCheck thread will never be interrupted because stepdown has already happened, so it will run on a secondary replica set node.

      CASE 2

      • metadataConsistencyCheck command is received on node1
      • metadataConsistencyCheck thread marks the opCtx as interruptible
      • node1 steps down before we can set the opCtx as interruptible
      • metadataConsistencyCheck thread doesn't check if the opCtx has been interrupted and returns the result to the user

      Attachments

        Activity

          People

            silvia.surroca@mongodb.com Silvia Surroca
            silvia.surroca@mongodb.com Silvia Surroca
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: