When a setShardVersion command, find command or write command that includes shard version information is sent to a shard server from another node (typically a mongos), it must also include the an optime on the config server no earlier than the earliest one in which that shard version information became available. Otherwise, a shard server refreshing its view of the sharding metadata from a secondary might read too-old metadata, and not see the new shard version.
- is depended on by
-
SERVER-20025 mongos fails to start if CSRS primary is not ismaster
-
- Closed
-
-
SERVER-20494 Enable reading from CSRS secondaries
-
- Closed
-
- is related to
-
-
- Closed
-
-
SERVER-20498 mongos should convey config optime information through the command metadata for all commands
-
- Closed
-
- related to
-
-
- Closed
-