[SERVER-8307] Use db-level lock when MapReduce input and output use a single DB Created: 23/Jan/13  Updated: 06/Dec/22  Resolved: 04/Feb/22

Status: Closed
Project: Core Server
Component/s: Concurrency, MapReduce
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Ben Becker Assignee: Backlog - Query Optimization
Resolution: Done Votes: 1
Labels: mapreduce
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-8579 Consolidate Mongod Lock/Resource Sche... Closed
Assigned Teams:
Query Optimization
Participants:

 Description   

In State::postProcessCollectionNonAtomic() and State::postProcessCollection(), only take a global write lock when necessary (e.g. if the input and output databases differ).



 Comments   
Comment by Esha Bhargava [ 04/Feb/22 ]

Closing these tickets as part of the deprecation of mapReduce.

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