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

Assert sharded commands can be accepted after waiting for clusterTime

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.2.0, 5.1.0-rc3
    • Affects Version/s: None
    • Component/s: Sharding
    • Fully Compatible
    • v4.0, v3.6
    • Server Serverless 2021-10-25, Server Serverless 2021-11-01, Server Serverless 2021-11-15

      Currently, a request's shard version is parsed and then the server immediately asserts that it can accept sharded commands (i.e. its sharding state is initialized). Instead, this should be checked after waiting for readConcern, so the server will have waited if afterClusterTime was given. This would allow a secondary that hasn't finished setting up its sharding state to accept a read with a valid shard version and afterClusterTime >= the optime of the insert of the shard identity document on the primary instead of throwing an error.

            Assignee:
            sophia.tan@mongodb.com Sophia Tan
            Reporter:
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: