[SERVER-41764] Shard can be removed while an ongoing migration is happening Created: 14/Jun/19  Updated: 29/Oct/23  Resolved: 02/Dec/19

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

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Randolph Tan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-39332 Prevent test from dropping collection... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2019-10-07, Sharding 2019-11-18, Sharding 2019-12-02, Sharding 2019-12-16
Participants:
Linked BF Score: 13

 Description   

Setup:

  • ShardA has no chunks/collections/database

Scenario:
1. Chunk migration from ShardZ to ShardA starts.
2. RemoveShard for ShardA starts.
3. Remove shards sees that there's no database/chunk for ShardA so proceeds to removing shard.
4. Chunk is now sent to ShardA after it has been "removed".



 Comments   
Comment by Githook User [ 02/Dec/19 ]

Author:

{'email': 'randolph@mongodb.com', 'name': 'Randolph Tan'}

Message: SERVER-41764 Serialize moveChunkCommit and removeShard
Branch: master
https://github.com/mongodb/mongo/commit/78db049cdbbacfd79c087f3569b1402257c0a1da

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