Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13191

Investigate changes in SERVER-44026: Remove global X lock for reIndex

    XMLWordPrintable

    Details

      Description

      Description

      Downstream Change Summary

      'reIndex' no longer takes a global lock. The strongest lock it now takes is an exclusive collection lock.

      Description of Linked Ticket

      Remove global X lock acquisition for reIndex. 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.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              ravind.kumar Ravind Kumar (Inactive)
              Reporter:
              backlog-server-pm Backlog - Core Eng Program Management Team
              Participants:
              Last commenter:
              Kay Kim (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                1 year, 7 weeks, 3 days ago
                Date of 1st Reply: