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

Tag server_status_metrics.js requires_document_locking

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.3.4
    • None
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2020-02-10
    • 44

    Description

      The new test added in SERVER-44711 for metrics.repl.network.oplogGetMoresProcessed requires_document_locking. This is because the test blocks oplog fetching on a failpoint while trying to do oplog writes. Under ephemeralForTest, the oplog writes (acquiring X lock) would conflict with the oplog reads (holding S lock) that's blocked on a failpoint.

      Normally that's not a problem because oplog writes should take MODE_IX locks and oplog reads should take MODE_IS when the storage engine supports document level locking.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: