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.
- is depended on by
-
SERVER-41389 Pause the oplog visibility thread in mode SECONDARY
- Closed
-
SERVER-45665 Make JournalFlusher flush on command and watiForWriteConcern asynchronously call waitUntilDurable through the JournalFlusher
- Closed
- is duplicated by
-
SERVER-44181 replicationBatchIsComplete() should make prompt the WiredTigerJournalFlusher thread to run instead of the _oplogJournalThreadLoop
- Closed