replicationBatchIsComplete() should prompt the WiredTigerJournalFlusher thread to run instead of the _oplogJournalThreadLoop

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.3.1
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • Execution Team 2019-11-04, Execution Team 2019-11-18
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      This project makes the WiredTigerOplogManager::_oplogJournalThreadLoop cease calling waitUntilDurable(), which is what replication wants to trigger after each round of batch application – so that readers with 'j' read concern can see the data as quickly as possible. Therefore, replicationBatchIsComplete should instead trigger the WiredTigerJournalFlusher thread, whose sole responsibility is to call waitUntilDurable(), to run immediately.

            Assignee:
            Dianna Hohensee (Inactive)
            Reporter:
            Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: