diff options
| author | Jason Chan <jason.chan@mongodb.com> | 2021-03-04 17:47:23 +0000 |
|---|---|---|
| committer | Evergreen Agent <no-reply@evergreen.mongodb.com> | 2021-03-06 00:38:16 +0000 |
| commit | f0a5b6384340c7b4b06c0e0e0edb32a5c007ae38 (patch) | |
| tree | 4c1e4f3b9e0a90e4453ca65c2f925809636bf848 /src/mongo/db/repl/oplog_applier_impl.cpp | |
| parent | 179b832e79916c45916eea111417990065fc003d (diff) | |
| download | mongo-f0a5b6384340c7b4b06c0e0e0edb32a5c007ae38.tar.gz | |
SERVER-54938 Only flush journal once per batch on secondary oplog application
Diffstat (limited to 'src/mongo/db/repl/oplog_applier_impl.cpp')
| -rw-r--r-- | src/mongo/db/repl/oplog_applier_impl.cpp | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/src/mongo/db/repl/oplog_applier_impl.cpp b/src/mongo/db/repl/oplog_applier_impl.cpp index 013fca2fdc8..a7df8ea39c7 100644 --- a/src/mongo/db/repl/oplog_applier_impl.cpp +++ b/src/mongo/db/repl/oplog_applier_impl.cpp @@ -554,13 +554,6 @@ StatusWith<OpTime> OplogApplierImpl::_applyOplogBatch(OperationContext* opCtx, } } - // Tell the storage engine to flush the journal now that a replication batch has completed. This - // means that all the writes associated with the oplog entries in the batch are finished and no - // new writes with timestamps associated with those oplog entries will show up in the future. We - // want to flush the journal as soon as possible in order to free ops waiting with 'j' write - // concern. - JournalFlusher::get(opCtx)->triggerJournalFlush(); - // Use this fail point to hold the PBWM lock and prevent the batch from completing. if (MONGO_unlikely(pauseBatchApplicationBeforeCompletion.shouldFail())) { LOGV2(21232, |