-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
v8.0
-
CAR Team 2024-12-23, CAR Team 2025-01-06
Removing a shard has two different phases: 1) draining all the data from the shard being removed and 2) commiting the operation.
Right now we don't provide any hint about how to move the data of track unsharded collections: due to its current implementation their are considered as if they were sharded, waiting until their only chunk is "moved". However, this won't happen as a regular sharded collection via moveChunk (and automatically done by the Balancer in most of the cases) but via moveCollection.
The purpose of this ticket is to provide more useful information about which data is still pending to be moved and which operations are expected to be used.
- depends on
-
SERVER-96213 Implement $listClusterCatalog using $_internalListCollections
- Closed
- fixes
-
SERVER-86421 Implement command to know which unsharded collections can be moved
- Closed
- is depended on by
-
SERVER-98655 Test when the removeShard command response reaches BSONObjMaxUserSize
- Blocked