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

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.7.0, 4.4.2
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • v4.4
    • Repl 2020-03-23
    • 50
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

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

              Created:
              Updated:
              Resolved:
              None
              None
              None
              None