Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Fully Compatible
-
ALL
-
24
Description
As exposed in our testing infrastructure, it seems like a config stepdown can cause a drop collection to be missed by both shards, leaving the cluster in a state where all shards agree the collection is sharded, but mongos knows it is not sharded.
Attachments
Issue Links
- is depended on by
-
SERVER-40172 Unblacklist merge_to_existing from sharding_csrs_continuous_config_stepdown
-
- Closed
-