-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Query Execution
-
Fully Compatible
-
ALL
-
v8.0, v7.0, v6.0
-
QE 2025-01-20, QE 2025-02-03, QE 2025-02-17
1. $out starts on a secondary. It creates a `temp` collection and starts writing to it.
2. Election happens and a new primary steps up. On stepup `temp` collections are dropped.
3. $out on the secondary continues running and will start targeting upcoming inserts to the new primary.
4. Since the `temp` collection has been dropped on step (2), the write at (3) will implicitly recreate it.
5. $out finishes successfully, but documents written before step (2) are missing.
- is related to
-
SERVER-85901 $out succeeds when source collection is concurrently dropped in a sharded cluster
-
- Closed
-
-
SERVER-75856 Support implicit database creation for $out when running aggregate on a mongos
-
- Closed
-
- related to
-
SERVER-38852 Failing $merge can leave zombie writes in the cluster
-
- Backlog
-
-
SERVER-43198 Zombie writes from failing $merge should not be able to re-create a collection
-
- Backlog
-
-
SERVER-101168 Complete TODO listed in SERVER-80853
-
- Backlog
-
-
SERVER-101144 Complete TODO listed in SERVER-80853
-
- Closed
-