-
Type: Improvement
-
Resolution: Done
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: MapReduce
-
None
-
Query Optimization
It seems like mapReduce jobs cause read starvation because of constant writes. This could be partially addressed with collection-level locking but having periods of yielding will help as well.
- related to
-
SERVER-8579 Consolidate Mongod Lock/Resource Scheduling Logic
- Closed