-
Type: Bug
-
Resolution: Unresolved
-
Priority: Minor - P4
-
None
-
Affects Version/s: 4.2.0
-
Component/s: Aggregation Framework, Sharding
-
Query Execution
-
ALL
-
Query 2019-09-23, Query 2019-10-07, Query 2019-10-21, Query 2019-11-04, QO 2022-08-22, QO 2022-09-05, QO 2022-09-19, QO 2022-10-03, QE 2022-10-31, QE 2022-11-14, QE 2022-11-28, QE 2022-12-12
SERVER-38852 describes a general problem of lingering operations which is probably much harder to solve. While investigating that we realized that $merge's writes are actually allowing an implicit creation of a collection. This may have been intentional to get the auto-create behavior for $merge, but it would be more robust to have the collection explicitly created, and that should be achievable.
- depends on
-
SERVER-44252 Delete implicit collection creation loop through the config server in sharding
- Closed
- is related to
-
SERVER-80853 $out on secondary node can produce incorrect results if primary steps down
- Needs Scheduling
-
SERVER-42430 Create whitelist of namespaces that are allowed to be created implicitly on shards
- Closed
- related to
-
SERVER-38852 Failing $merge can leave zombie writes in the cluster
- Backlog