[SERVER-6563] Improve consistency of non-primary reads in a sharded cluster Created: 23/Jul/12 Updated: 07/Mar/14 Resolved: 07/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Sharding |
| Affects Version/s: | 2.0.6, 2.1.2 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Tyler Brock | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
One example of this is the appearance of duplicate documents being returned for in a sharded cluster – if migrates have failed and not been cleaned up. Only the primary node has cluster-aware connections (setShardVersion'd) from the mongos instances, which will hide unowned data. |