SERVER-43060 CheckReplDBHashInBackground should retry the dbHash command on WriteConflicts in debug builds

1 files changed, 8 insertions, 0 deletions

diff --git a/jstests/hooks/run_check_repl_dbhash_background.js b/jstests/hooks/run_check_repl_dbhash_background.js
index 66a85c43c36..1a61b3c2785 100644
--- a/jstests/hooks/run_check_repl_dbhash_background.js
+++ b/jstests/hooks/run_check_repl_dbhash_background.js
@@ -309,6 +309,14 @@ function checkReplDbhashBackgroundThread(hosts) {
                 hasTransientError = true;
             }
 
+            // In debug builds, read-only operations can receive write conflicts when the storage
+            // engine cache is full. Since dbHash holds open a read snapshot for an extended period
+            // of time and pulls all collection data into cache, the storage engine may abort the
+            // operation if it needs to free up space. Try again after space has been freed.
+            if (e.code === ErrorCodes.WriteConflict && buildInfo().debug) {
+                hasTransientError = true;
+            }
+
             return hasTransientError;
         };