[SERVER-4604] inserts need better handling of version changes Created: 03/Jan/12 Updated: 11/Jul/16 Resolved: 05/Jan/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 2.1.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
In at least certain cases, inserts do not re-check the shard they were sent to when receiving a bad version in checkShardVersion. This can lead to misdirected inserts if migrations are heavy, particularly if migrations are taking a lot of resources. (this, along with Solution - probably refactor this code in line with the new pcursor stuff. |
| Comments |
| Comment by auto [ 05/Jan/12 ] |
|
Author: {u'login': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: also first step of getting all-inclusive sharded insert method |