Need to make sure we are checking the shard version correctly and return the correct error, stale config.
We should ensure that this is done for findAndModify and any other update callers.
Greg suggests that we should investigate if all version checks can be done directly in the update code.
- duplicates
-
SERVER-17805 logOp / OperationObserver should always check shardversion
- Closed
- is duplicated by
-
SERVER-11678 Improve shard version checking for updates (esp. yielding)
- Closed
- is related to
-
SERVER-14669 Updates/deletes on sharded collections shouldn't affect orphan documents
- Closed
-
SERVER-17585 Enforce shard version after yields on versioned (single) deletes
- Closed