SERVER-62592 Make config server update more resilient for clearJumboFlag test of timeseries collection

(cherry picked from commit cbd34a8fef51c462300982b997118c790f6de792)

1 files changed, 4 insertions, 1 deletions

diff --git a/jstests/sharding/timeseries_sharding_admin_commands.js b/jstests/sharding/timeseries_sharding_admin_commands.js
index 0a0f0da2d0f..6a90a4b011c 100644
--- a/jstests/sharding/timeseries_sharding_admin_commands.js
+++ b/jstests/sharding/timeseries_sharding_admin_commands.js
@@ -263,7 +263,10 @@ function assertRangeMatch(savedRange, paramRange) {
     const configDB = mongo.s0.getDB('config');
     const collDoc = configDB.collections.findOne({_id: bucketNss});
     let chunkDoc = configDB.chunks.findOne({uuid: collDoc.uuid});
-    configDB.chunks.update({_id: chunkDoc._id}, {$set: {jumbo: true}});
+    assert.retryNoExcept(() => {
+        assert.commandWorked(configDB.chunks.update({_id: chunkDoc._id}, {$set: {jumbo: true}}));
+        return true;
+    }, "Setting jumbo flag update failed on config server", 10);
     chunkDoc = configDB.chunks.findOne({_id: chunkDoc._id});
     assert(chunkDoc.jumbo);
     assert.commandWorked(