-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
ALL
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)
- depends on
-
SERVER-4537 better protect all sharding admin operations from simultaneous commands
- Closed
- is duplicated by
-
SERVER-8838 removeRange() implicitly re-creates a database if database does not exist
- Closed