When dropping a collection, we abort any index builds on that collection before actually performing the drop. However, when the _shardsvrDropCollectionParticipant command is run with fromMigrate set to true (which currently is the case on all non-primary shards participating in the drop), this index build abort logic gets bypassed.
- is caused by
-
SERVER-69603 Do not report drop events as part of shardCollection
-
- Closed
-
-
SERVER-71085 DropCollectionCoordinator should only report a single drop event through the Primary Shard oplog
-
- Closed
-