-
Type: Question
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.4.9, 2.6.0
-
Component/s: MapReduce
-
None
When writing results to an output collection, the map/reduce engine acquires a global write lock, effectively blocking the server for all other operations. Even when the nonAtomic option is used, the global lock is acquired for every single document that is written, and since this happens pre-emptively, the effect is very much the same.
This effectively prevents any kind of concurrency while doing map/reduce computations and should therefore be changed.
- duplicates
-
SERVER-7831 m/r: reduce post processing: reduce lock time with "nonAtomic" option
- Backlog
- related to
-
SERVER-13552 remove unnecessary global lock during "replace" out action
- Backlog