[SERVER-21076] Write tests to ensure that operations using DBDirectClient handle shard versioning properly Created: 22/Oct/15 Updated: 25/Jan/17 Resolved: 14/Dec/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.1, 3.3.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | test-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Completed: | |||||||||
| Sprint: | Sharding C (11/20/15), Sharding D (12/11/15), Sharding E (01/08/16) | ||||||||
| Participants: | |||||||||
| Description |
|
Since 2f7b99c780cfdce94b2888ddc8e078536af459a6 we disable all shard version checking while in DBDirectClient. We need to make sure that all operations that use DBDirectClient while operating on sharded collections (maybe just map-reduce?) properly do their own shard versioning handling and weren't relying on shard version checking to happen via DBDirectClient. As for what the test could look like, I was thinking of something along the line of doing a map-reduce on a stale mongos right after a chunk migration and purposefully creating some orphaned data on the former chunk owner and making sure the map reduce sees the proper data |
| Comments |
| Comment by Githook User [ 14/Dec/15 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: (cherry picked from commit 62f3810a0a28007df14bd4e3f5a3282ab01a60c7) |
| Comment by Githook User [ 14/Dec/15 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |