-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Execution
-
ALL
-
QE 2023-08-07, QE 2023-08-21, QE 2023-09-04, QE 2023-09-18, QE 2023-10-02, QE 2023-10-16, QE 2023-10-30, QE 2023-11-13, QE 2023-11-27, QE 2023-12-11, QE 2023-12-25, QE 2024-01-08
In SERVER-33700 we decided to skip dropping database or dropping collection when the invalidated_cursors.js FSM run on sharded clusters. The reason was that after doing those drops the test was failing to perform inserts with error "unable to target write op for collection ... caused by ... database not found".
Originally we correlate this error to a bug affecting dropping collections/databases on sharded cluster SERVER-17397. Considering that this bug have been fixed in 5.0 we should now remove these exceptions in the test.
- depends on
-
SERVER-83547 Unify behavior for explain().aggregate() when running on a nonexistent database
-
- Closed
-
- is caused by
-
SERVER-33700 Adapt invalidate_cursors.js to run killOp and killCursors on active getMores on sharded clusters
-
- Closed
-
- is related to
-
-
- Closed
-
- related to
-
-
- Closed
-