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

Shard registry might be accessed before initialization

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.0.1, 5.0.10, 6.1.0-rc0
    • 5.0.7, 6.0.0-rc6
    • None
    • None
    • Fully Compatible
    • ALL
    • v6.0, v5.3, v5.0
    • Sharding EMEA 2022-05-30
    • 6

    Description

      SERVER-57280 introduced a mechanism that tried to prevent accesses to the shard registry via the getShardNoReload before setting up the shard registry. However, there is a race that can happen after setting the isUp variable from a thread that is performing the first refresh, and another thread using the non causally consistent API, that might result on the shard registry not finding any shard if the node have been recently started.

      Attachments

        1. BF-23456_repro.patch
          5 kB

        Activity

          People

            tommaso.tocci@mongodb.com Tommaso Tocci
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: