Transaction history iterator shouldn't yield on next()

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.12
    • Affects Version/s: None
    • Component/s: Querying, Replication
    • None
    • Fully Compatible
    • ALL
    • Query 2019-06-03
    • 17
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Justin Seyster
            Reporter:
            Siyuan Zhou
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: