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

Wrong comparison might make shard registry accessed before initialization

    • Type: Icon: Bug Bug
    • Resolution: Declined
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • ALL
    • v6.0, v5.0
    • Sharding EMEA 2022-06-13, Sharding EMEA 2022-06-27

      SERVER-66658 intended to solve a race between two different threads trying to access the shard registry while it was being refreshed, however, now we might return that the shard registry is up when it isn't, because comparing the shard registry time with Time() will always be false due to the forceReloadIncrement component.

      We should get the topology version component and only compare that with Timestamp() instead.

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

              Created:
              Updated:
              Resolved: