[SERVER-26198] Balancer can return Status::OK for a manual moveChunk while the migration is still waiting on waitForDelete Created: 20/Sep/16  Updated: 19/Nov/16  Resolved: 21/Sep/16

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

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
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2016-10-10
Participants:
Linked BF Score: 0

 Description   

Mongos sends moveChunk command, balancer on config server schedules it, then config server steps down, interrupting the balancer at the point where the migration has been committed but waitForDelete has not finished on the shard. MigrationManager::executeManualMigration does a check on failure to see if the moveChunk was actually successful, and if so, sets the Status to OK.

If this is the case, we should not set Status to OK if the error is identifiably due to config interrupt/stepdown.



 Comments   
Comment by Githook User [ 21/Sep/16 ]

Author:

{u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}

Message: SERVER-26198 always return retriable error if manual moveChunk is interrupted on balancer
Branch: master
https://github.com/mongodb/mongo/commit/7dd2b1a22ca7ca11a697c54e682ea68383ad8138

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