-
Type: Improvement
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
This would solve the issue described in SERVER-50143. We should also add some visibility on how many documents are left (either via the removeShard response object or metrics or some other means)
- is fixed by
-
SERVER-50143 Removing a shard with in-progress transaction coordinators can leave transactions on participants permanently in prepare
- Backlog
- is related to
-
SERVER-50143 Removing a shard with in-progress transaction coordinators can leave transactions on participants permanently in prepare
- Backlog
-
SERVER-89179 Create database concurrent with removeShard can create the new db on a removed shard
- Closed