[SERVER-4724] removeShard needs to take into account asynchronous document deletion after migrate Created: 19/Jan/12  Updated: 08/Mar/13  Resolved: 08/Mar/13

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

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-4537 better protect all sharding admin ope... Closed
Duplicate
is duplicated by SERVER-8838 removeRange() implicitly re-creates a... Closed
Operating System: ALL
Participants:

 Description   

A shard may be removed by mongos, but open cursors may remain on the final migration's data waiting to be deleted. So long as these cursors are open, the data will not be deleted and the shard cannot be re-added. Need to also verify that all databases will be removed in this case.

We should probably check for this case explicitly and check that the shard's sharded databases are removed before removing the shard. (Say that 5 times fast)


Generated at Thu Feb 08 03:06:47 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.