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

Stop sending init form of setShardVersion

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.3.4
    • Component/s: Sharding
    • Fully Compatible
    • Sharding 2017-01-02, Sharding 2017-02-13

      In addition, mongos now needs to start sending setShardVersion (0,0) before sending requests to unsharded collections, otherwise, the connection will never have ShardedConnectionInfo and no version checking will take place for that connection. In other words, if the collection was actually sharded, the shard will not throw a stale shard version exception.

            Assignee:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: