SERVER-60424 Have TenantOplogFetcher recreate cursors with initial maxTimeout

(cherry picked from commit 9c229633f98be337d0fe676c2b4b7b1aa5cf4f61)

1 files changed, 5 insertions, 1 deletions

diff --git a/src/mongo/db/repl/oplog_fetcher.cpp b/src/mongo/db/repl/oplog_fetcher.cpp
index c7977f30ef8..b3f06150854 100644
--- a/src/mongo/db/repl/oplog_fetcher.cpp
+++ b/src/mongo/db/repl/oplog_fetcher.cpp
@@ -665,7 +665,11 @@ StatusWith<OplogFetcher::Documents> OplogFetcher::_getNextBatch() {
         Timer timer;
         if (!_cursor) {
             // An error occurred and we should recreate the cursor.
-            auto status = _createNewCursor(false /* initialFind */);
+            // The OplogFetcher uses an aggregation command in tenant migrations, which does not
+            // support tailable cursors. When recreating the cursor, use the longer initial max time
+            // to avoid timing out.
+            const bool initialFind = _config.forTenantMigration;
+            auto status = _createNewCursor(initialFind /* initialFind */);
             if (!status.isOK()) {
                 return status;
             }