Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-45626

Consistent Oplog Locking Rules

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.7.0, 4.4.2
    • None
    • Fully Compatible
    • v4.4
    • Repl 2020-03-09, Repl 2020-03-23
    • 23

    Description

      In principle we should only need the Global IS/IX lock to read/write the oplog. However, see SERVER-44906, we're inconsistent. Furthermore, there are cases our code requires a DB and Collection lock in order to get a Collection pointer to the oplog, although this is not fundamentally necessary.

      Inconsistent locking invites mistakes: deadlocks, race conditions, and unnecessary waiting.

      Attachments

        Issue Links

          Activity

            People

              lingzhi.deng@mongodb.com Lingzhi Deng
              dbeng-pm-bot PM Bot
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: