[DOCS-12472] Docs for SERVER-38311: Investigate changing host type requirement for $out Created: 14/Feb/19  Updated: 13/Nov/23  Resolved: 29/Jul/19

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.1.9, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Kay Kim (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-38311 Investigate changing host type requir... Closed
Participants:
Days since reply: 5 years ago
Epic Link: DOCS: 4.2 Server/Tools

 Description   

Description

Description:

The $out stage can now be run in parallel on all shards if
1) the targeted collection is sharded (so only modes "insertDocuments" or "replaceDocuments", as of this writing)
2) The collection of the aggregation (e.g. "foo" in db.foo.aggregate([{$out: "bar"}])) is sharded
3) There is no stage which otherwise "forces a split" of the pipeline like a $group.

Engineering Ticket Description:

During the design we agreed to the following change in merging policy:

We will change the pipeline splitting logic such that $out is not forced to execute in the merger part of the pipeline, and does not cause the pipeline to split. If $out is preceded by stages that can all execute in the shards part, then each shard will be responsible for dispatching writes to the correct shard.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)


Generated at Thu Feb 08 08:05:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.