Details
-
Bug
-
Resolution: Won't Fix
-
Major - P3
-
None
-
None
-
None
-
Sharding NYC
-
ALL
-
9
Description
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.
Attachments
Issue Links
- related to
-
SERVER-73751 movePrimary shouldn't create indexes for sharded collections
-
- Closed
-