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

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

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Storage
    • None
    • Storage Execution

    Description

      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.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: