Remove global X lock for mapReduce

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • v4.2
    • Query 2019-11-18
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Remove global X lock acquisition for mapReduce. This is because acquiring global lock in X mode can be blocked by prepared transactions. The enqueued global X lock can block oplog queries which need the global IS lock. If these oplog queries and the data replication are needed to satisfy the prepared transaction's write concern, then the prepare transaction and replication cannot make progress. Thus a deadlock occurs.

      Alternatively, if removing global X lock is not an option, deprecate the command or make sure it won't be blocked on prepare transactions.

              Assignee:
              James Wahlin
              Reporter:
              Lingzhi Deng
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: