[SERVER-26063] shard movechunk command should not register migrations for chunks it does not have Created: 12/Sep/16  Updated: 12/Sep/16  Resolved: 12/Sep/16

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

The Balancer may attempt to recover migrations that it already told the mongos were successful. For example, as soon as a config server is stepped down, it can still return successful movechunk results, but is unable to remove the migration document so that migration gets picked up on balancer recovery on the new primary.

This poses a problem because the mongos (our JS test via the mongos) can move on to the next moveChunk and get a conflicting operation error from the shard because it registered the old migration before checking whether it was actually going to do it – whether it has that chunk to move.


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