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

AutoGetOplog doesn't acquire collection IX lock correctly for non-document-locking engines

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.7.0, 4.4.2
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.4
    • Sprint:
      Repl 2020-03-23
    • Linked BF Score:
      50

      Description

      In kLogOp mode, AutoGetOplog only acquires collection lock for non-document-locking storage engines if it is not already held. However, AutoGetOplog uses ShouldNotConflictWithSecondaryBatchApplicationBlock which makes isCollectionLockedForMode always return true, resulting in skipping collection lock for kLogOp mode under non-document-locking storage engines.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              lingzhi.deng Lingzhi Deng
              Reporter:
              lingzhi.deng Lingzhi Deng
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: