[SERVER-22203] remove shardVersion information and usages from BatchedCommandRequest Created: 15/Jan/16 Updated: 16/Mar/16 Resolved: 08/Mar/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Sharding F (01/29/16), Sharding 10 (02/19/16), Sharding 11 (03/11/16) | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
| Comments |
| Comment by Esha Maharishi (Inactive) [ 08/Mar/16 ] |
|
Note: a change was made to when mongod does shard versioning to allow idempotent multiUpdates to eventually succeed if retried until all matching documents were updated. Before: If a stale mongos targeted a single shard for a multiUpdate or multiRemove, but the chunk had moved, the update or remove would never succeed from that mongos (unless/until the mongos refreshed its metadata due to some other operation). After: The above case now succeeds, since versioning is done if a single shard is targeted. On the other hand, if a stale mongos targets multiple shards, but a chunk has moved, the mongos will receive a staleShardVersion and retry the request to (all) shards, allowing the request to eventually succeed. However, in this case, a non-idempotent update may get applied more than once. |
| Comment by Githook User [ 08/Mar/16 ] |
|
Author: {u'name': u'Esha Maharishi', u'email': u'esha.maharishi@mongodb.com'}Message: |