SERVER-45423 Use isRetriableError instead of isNetworkError for transient errors in initial sync

1 files changed, 7 insertions, 7 deletions

diff --git a/src/mongo/db/repl/initial_syncer.h b/src/mongo/db/repl/initial_syncer.h
index 399fdd57c54..54506e384fe 100644
--- a/src/mongo/db/repl/initial_syncer.h
+++ b/src/mongo/db/repl/initial_syncer.h
@@ -596,17 +596,17 @@ private:
         const stdx::lock_guard<Latch>& lock, std::shared_ptr<OnCompletionGuard> onCompletionGuard);
 
     /**
-     * Check if a status is one which means there's a network error and we should retry the current
-     * operation, and records whether an operation is currently being retried.  Note this can only
-     * handle one operation at a time (i.e. it should not be used in both parts of the "split"
-     * section of Initial Sync)
+     * Check if a status is one which means there's a retriable error and we should retry the
+     * current operation, and records whether an operation is currently being retried.  Note this
+     * can only handle one operation at a time (i.e. it should not be used in both parts of the
+     * "split" section of Initial Sync)
      */
-    bool _shouldRetryNetworkError(WithLock lk, Status status);
+    bool _shouldRetryError(WithLock lk, Status status);
 
     /**
-     * Indicates we are no longer handling a network error.
+     * Indicates we are no longer handling a retriable error.
      */
-    void _clearNetworkError(WithLock lk);
+    void _clearRetriableError(WithLock lk);
 
     /**
      * Checks the given status (or embedded status inside the callback args) and current data