In at least certain cases, inserts do not re-check the shard they were sent to when receiving a bad version in checkShardVersion. This can lead to misdirected inserts if migrations are heavy, particularly if migrations are taking a lot of resources. (this, along with SERVER-4603, may be impacting mrShardedOutput.js/bigMapReduce.js).
Solution - probably refactor this code in line with the new pcursor stuff.
- is duplicated by
-
SERVER-6781 Document in the wrong shard.
- Closed
- is related to
-
SERVER-5200 slowNightly tests failing on sharding_balance4.js
- Closed
-
SERVER-5749 updates need better handling of version changes (sharding_balance4.js failure)
- Closed