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

Always skip OperationShardingState initialization if the read concern is `available`

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.0-rc0
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Sharding 2017-10-23
    • Linked BF Score:
      0

      Description

      Currently, the check for shard version mismatch consults both the operation's state (when shardVersion parameter is attached to the command) and the connection's sharding info (when the command is run over a sharded collection).

      Instead of looking up one or the other at version check time, we should consolidate the code which determines what shardVersion a request must use to happen in one place so that we can add additional checks that for example requests over sharded connections do not contain shard version.

        Attachments

          Activity

            People

            Assignee:
            kaloian.manassiev Kaloian Manassiev
            Reporter:
            kaloian.manassiev Kaloian Manassiev
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: