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

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

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 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

      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@mongodb.com Dianna Hohensee (Inactive)
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: