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-16 16:57:07 +0000 |
| commit | 2b9ffef47ff730bbbea63feca07e871393856be5 (patch) | |
| tree | 7551a4e6314a8b01156b096fc798204e5f861144 | |
| parent | c60f7a4f2d00d26aeb79720fdc4e0080d3df38c1 (diff) | |
| download | mongo-2b9ffef47ff730bbbea63feca07e871393856be5.tar.gz | |
SERVER-54938 Only flush journal once per batch on secondary oplog application
(cherry picked from commit f0a5b6384340c7b4b06c0e0e0edb32a5c007ae38)
| -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 ca5a51fa8e2..46db4e27794 100644 --- a/src/mongo/db/repl/oplog_applier_impl.cpp +++ b/src/mongo/db/repl/oplog_applier_impl.cpp @@ -735,13 +735,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, |