[SERVER-13364] geoNear command doesn't handle versioning correctly Created: 26/Mar/14 Updated: 06/Dec/22 Resolved: 08/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Geo, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Siyuan Zhou | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||||
| Description |
|
geoNear command doesn't handle versioning correctly, so it will return duplicated or missing results if there is a concurrent chunk migration (or a shard has orphaned documents). |
| Comments |
| Comment by Esha Maharishi (Inactive) [ 07/Sep/17 ] |
|
Reassigning to the sharding backlog and moving to the 'Safe Secondary Reads' epic as 3.5 desired. If/when geoNear is fixed to be versioned (which should be a small change - just attach ChunkVersion::UNSHARDED() to the outgoing geoNear requests and/or move geoNear to use scatterGather()), the following safe secondary reads tests should be updated: jstests/sharding/safe_secondary_reads_drop_recreate.js These tests all explicitly check that geoNear's behavior is unversioned. |