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

Make ARS use causally consistent ShardRegistry::getShard() function

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.0.1, 5.0.10, 5.3.3, 6.1.0-rc0
    • Affects Version/s: 5.3.0-rc4, 5.0.9, 6.0.0-rc13
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • v6.0, v5.3, v5.0
    • Sharding EMEA 2022-06-27, Sharding EMEA 2022-07-11
    • 20

      Currently the ARS uses the non-causally consistent ShardRegistry::getShardNoReload() function to retrieve the target shard.

      This function doesn't guarantee that:


      The ARS should use the causally consistent counter-part function  ShardRegistry::getShard().

      A first attempt to fix this showed that is not feasible to call this blocking function using the internally stored operation context. As alternative solution we could provide a async version of the ShardRegistry::getShard that will be used in the ARS future-chain that implements the remote request scheduling.

            tommaso.tocci@mongodb.com Tommaso Tocci
            tommaso.tocci@mongodb.com Tommaso Tocci
            0 Vote for this issue
            3 Start watching this issue