-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: 8.0.0
-
Component/s: None
-
None
-
Query Execution
-
Fully Compatible
-
v8.0
-
QE 2024-10-28, QE 2024-11-11, QE 2024-11-25, QE 2024-12-09, QE 2024-12-23
-
0
It is not garunteed that a database drop results in a StaleDB error that we are trying to handle here https://github.com/mongodb/mongo/blob/c41e87779e5dc89aa2f939d6a7b52aea1a650740/src/mongo/db/pipeline/document_source_writer.h#L297 furthermore we are forcing a refresh on the database which can have performance implications on other operations involving that database in order to handle movePrimary situation.
in this ticket we are trying to attempt a short term solution for $out that still has all of the old known pre 8.0 bugs but doesn't have any new correctness or performance bugs
- duplicates
-
SERVER-94889 Investigate suspicious usage of isSharded() condition
-
- Closed
-
- is caused by
-
-
- Closed
-
- is related to
-
-
- Backlog
-
-
-
- Closed
-
-
-
- Closed
-