[SERVER-21497] Disable yield_geo_near_dedup.js FSM workload when balancer is running Created: 17/Nov/15 Updated: 25/Nov/15 Resolved: 17/Nov/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 3.2.0-rc2 |
| Fix Version/s: | 3.2.0-rc4 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Max Hirschhorn | Assignee: | Max Hirschhorn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | QuInt C (11/23/15) | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
The yield_geo_near_dedup.js workload tests that documents returned by the geoNear command are deduplicated by their RecordId. It assumes the pair (_id, timesInserted) uniquely determines a RecordId; however, that isn't the case in a sharded system where documents can move between shards. Since mongos cannot return information about which shard the document came from, i.e. to deduplicate by the triplet (shard #, _id, timesInserted), the assertions that the workload makes may fail when the balancer is running concurrently. |
| Comments |
| Comment by Githook User [ 17/Nov/15 ] |
|
Author: {u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}Message: |