-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 5.0.14, 6.0.3, 6.2.0-rc4
-
Component/s: Sharding
-
Fully Compatible
-
v6.2, v6.0, v5.0
-
Sharding EMEA 2022-11-28, Sharding EMEA 2022-12-12, Sharding EMEA 2022-12-26, Sharding EMEA 2023-01-09, Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06
-
10
In many sharded suites we exclude tests that perform drop collection/database because of SERVER-17397. In fact before 5.0 dropping a collection/database was not resilient to failures.
Since SERVER-17397 was fixed in 5.0 we should stop excluding those tests.
- causes
-
SERVER-77039 Re-blacklist map_reduce_drop.js from SERVER-71368 changes
- Closed
- depends on
-
SERVER-71597 Fix race condition on createDatabase for case sensitive dbName
- Closed
-
SERVER-72877 Mongos retargeting logic in stepdown hooks should skip views
- Closed
-
SERVER-72879 Recreation of same database with different cases could lead to database unavailability
- Closed
-
SERVER-73389 Checkpoint vector clock in drop database coordinator
- Closed
- is duplicated by
-
SERVER-71218 Review test wrongly blacklisted because of [solved] SERVER-17397
- Closed