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

Transaction history iterator shouldn't yield on next()

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.12
    • Component/s: Querying, Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Query 2019-06-03
    • Linked BF Score:
      17

      Description

      Transaction iterator is used in SyncTail::multiApply() to fetch the oplog chain of unprepared transactions. However yielding doesn't support PBWM lock, which is held by sync tail. We don't need yielding when reading transaction history since it's always a point query.

        Attachments

          Activity

            People

            Assignee:
            justin.seyster Justin Seyster
            Reporter:
            siyuan.zhou Siyuan Zhou
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: