[DOCS-12566] Indicate unsupported mapReduce scenarios Created: 22/Mar/19  Updated: 13/Nov/23

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

Type: Task Priority: Major - P3
Reporter: Blake Oler Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-37679 Concurrent sharded fuzzers should not... Closed
Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

Description

We have discovered a flaw in mapReduce, but we don't intend on dedicating resources to it at the moment. Performing the following actions can potentially cause a crash.

  1. All concurrent mapReduces to sharded output collections with the reduce option.
  2. All concurrent mapReduces to sharded output collections with the replace option that output to an empty collection.
  3. All concurrent mapReduces to sharded output collections with the merge option that output to an empty collection.

Scope of changes

We should indicate that those former mapReduces are unsupported.

Include general advisory to use aggregation instead of mapreduce for operations against sharded collections.

Impact to Other Docs

MVP (Work and Date)

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



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

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