[SERVER-26372] If a chunk has been split since a moveChunk was sent to a shard, you can get an error message with "This indicates corrupted metadata" Created: 28/Sep/16  Updated: 06/Oct/16  Resolved: 06/Oct/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Improvement 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
is related to SERVER-26396 MigrationSourceManager isn't using Co... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2016-10-31
Participants:
Linked BF Score: 0

 Description   

In the MigrationSourceManager there is a check here that assumes if the shard has a chunk with the minKey, but doesn't have a maxKey corresponding to the command's maxKey, that the metadata is corrupted.

We should check whether there's another chunk with a minKey matching the maxKey, and if so, assume that the chunk was split and return a more benign error message.



 Comments   
Comment by Dianna Hohensee (Inactive) [ 06/Oct/16 ]

This ticket was incidentally fixed by SERVER-26396

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