[SERVER-25686] Config server manual move chunk request won't rejoin migrations if they waitForDelete Created: 18/Aug/16  Updated: 28/Sep/16  Resolved: 22/Aug/16

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

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Dianna Hohensee (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2016-08-29
Participants:
Linked BF Score: 0

 Description   

The config server's manual move chunk internal call _configsvrMoveChunk is intended to be idempotent in the absence of other metadata changing activity on the system and the continuous stepdown suite relies on this behaviour.

However, in the case where waitForDelete is specified and the move chunk operation on the shard is already at the stage where cleanup happens, _configsvrMoveChunk may report a retried operation as successful before the cleanup has completed.

This causes tests, which rely on the range cleanup to complete to fail when run under the continuous config stepdown suite.



 Comments   
Comment by Githook User [ 22/Aug/16 ]

Author:

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

Message: SERVER-25686 send all moveChunk commands through to the shard to wait for waitForDelete
Branch: master
https://github.com/mongodb/mongo/commit/d45804b3bf5c336ab5943bff163d1e0e5fcfd3a6

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