[SERVER-21650] Duplicate _id when reading from secondaries on a sharded cluster Created: 24/Nov/15 Updated: 24/Nov/15 Resolved: 24/Nov/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.0.7 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | giser | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
We find there the same _id exist on different sharding, but we set different mode in client to query this _id data ,there will be different results, such as when we use the primary mode query returns only one data { "_id" : ObjectId("561fce30fd902e1234426ba7"), "adGroupId" : 6025696187079 }when we use secendaryPreferred or primaryPreferred mode query returns two data { "_id" : ObjectId("561fce30fd902e1234426ba7"), "adGroupId" : 6025696187079 } { "_id" : ObjectId("561fce30fd902e1234426ba7"), "adGroupId" : 6025696187079 } |
| Comments |
| Comment by Ramon Fernandez Marina [ 24/Nov/15 ] |
|
Thanks for your report giser. Secondary reads on sharded clusters may return orphaned documents, please see Regards, |