Global Lock in Reduce Phase of Map/Reduce

XMLWordPrintableJSON

    • Type: Question
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.4.9, 2.6.0
    • Component/s: MapReduce
    • None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • 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.

              Assignee:
              Mathias Stearn
              Reporter:
              Andre Spiegel
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: