-
Type: Bug
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Sharding NYC
-
ALL
-
9
I don't see any obvious checks done in the Cloner code before calling createIndexesOnEmptyCollection, which may hit an invariant if the collection exists. Cloner should error and log more information in such scenarios.
- related to
-
SERVER-73751 movePrimary shouldn't create indexes for sharded collections
- Closed