[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:
Related
related to SERVER-26372 If a chunk has been split since a mov... Closed
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: SERVER-26396 converted unnecessarily alarming error message in MigrationSourceManager into a benign one.
Branch: master
https://github.com/mongodb/mongo/commit/61b928dccc9b31d638c96dbe82713f291ffe2b5d

Generated at Thu Feb 08 04:11:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.