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

Don't acquire locks on oplog when writing oplog entries

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.4, 4.1.3
    • Component/s: Replication, Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.0, v3.6
    • Sprint:
      Storage NYC 2018-08-27
    • Case:
    • Linked BF Score:
      36

      Description

      Since the oplog can never be dropped, there's no need to hold an IX lock on the oplog when writing into it.

        Attachments

          Issue Links

          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-35367 Hold locks in fewer callers of waitForAllEarlierOplogWritesToBeVisible()

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-36883 support non-doc-locking storage engines in SERVER-36534

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-40498 Writing transaction oplog entries must not take locks while holding an oplog slot

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-36514 Hold lock on oplog as soon as optime is reserved

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: