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

Lock-free reads on a shard secondary node can mismatch the storage snapshot and shard version

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Gone away
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • Sharding EMEA
    • ALL

    Description

      Lock-free reads first open a storage engine snapshot and later check that the shard version the router sent matches the installed one. Because there's no shardVersion check before opening the snapshot, the snapshot could correspond to a different sharding placement. This will cause the query to not notice a placement mismatch or to be executed with a sharding filter that does not match the storage engine snapshot.

      Attachments

        Activity

          People

            backlog-server-sharding-emea [DO NOT USE] Backlog - Sharding EMEA
            jordi.serra-torrens@mongodb.com Jordi Serra Torrens
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: