[SERVER-26396] MigrationSourceManager isn't using CollectionMetadata::getNextChunk correctly for error logging. Created: 29/Sep/16 Updated: 19/Nov/16 Resolved: 05/Oct/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Sharding 2016-10-10 | ||||||||
| Participants: | |||||||||
| Description |
|
The logic in the MigrationSourceManager here should be fixed. CollectionMetadata::getNextChunk won't necessarily return a chunk with the minKey given, but can also return the next chunk with a minKey higher than the given one. The use in MigrationSourceManager does not seem to account for this. |
| Comments |
| Comment by Githook User [ 05/Oct/16 ] |
|
Author: {u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}Message: |