SERVER-45565: Modified Oplog Batcher behavior to process large transaction oplog entries in separate batches

 create mode 100644 jstests/noPassthrough/large_txn_correctness.js

1 files changed, 13 insertions, 3 deletions

diff --git a/src/mongo/db/repl/oplog_entry.h b/src/mongo/db/repl/oplog_entry.h
index d17c0a4c512..9f4d6c5ba0c 100644
--- a/src/mongo/db/repl/oplog_entry.h
+++ b/src/mongo/db/repl/oplog_entry.h
@@ -317,6 +317,11 @@ public:
     }
 
     /**
+     * Returns whether if the oplog entry is the last applyOps in a multiple-entry transaction.
+     */
+    bool isEndOfLargeTransaction() const;
+
+    /**
      * Returns if this is a prepared 'commitTransaction' oplog entry.
      */
     bool isPreparedCommit() const {
@@ -334,10 +339,15 @@ public:
     }
 
     /**
-     * Returns whether the oplog entry represents an applyOps with a commnd inside. This will occur
-     * if a multi-document transaction performs a command.
+     * Returns whether the oplog entry represents a single oplog entry transaction.
+     */
+    bool isSingleOplogEntryTransaction() const;
+
+    /**
+     * Returns whether the oplog entry represents an applyOps with a command inside. This is only
+     * for transactions with only one oplog entry.
      */
-    bool isTransactionWithCommand() const;
+    bool isSingleOplogEntryTransactionWithCommand() const;
 
     /**
      * Returns if the oplog entry is for a CRUD operation.