mongodb/mongo
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

SERVER-125945 Fix checkIndexesConsistentAcrossCluster to retry on HostUnreachable (#53142)

Browse Source 
GitOrigin-RevId: 5419a8218837db0d805e03bb501f69952dbafdd0
This commit is contained in:
wolfee 2026-05-05 13:37:05 +02:00 committed by MongoDB Bot
parent 83064e653a
commit 91c6488bc2
1 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
jstests/libs/check_cluster_index_consistency_helpers.js
View File

@ -29,8 +29,15 @@ export var ClusterIndexConsistencyChecker = (function () {
// ShardRegistry reloads after choosing which shards to target and a chosen
// shard is no longer in the cluster. This error should be transient, so it
// can be retried on.
if (e.code === ErrorCodes.ShardNotFound) {
jsTest.log.info("Retrying $indexStats aggregation on ShardNotFound error", {error: e});
//
// Getting the indexes can also fail with HostUnreachable if the mongos
// routes to a node that stepped down since the mongos last polled its SDAM
// state (e.g. after replSetStepUp). The mongos intentionally rewrites
// NotPrimary shard errors as HostUnreachable so that the client retries
// without triggering an SDAM state change. Once the mongos refreshes its
// topology the retry will succeed.
if (e.code === ErrorCodes.ShardNotFound || e.code === ErrorCodes.HostUnreachable) {
jsTest.log.info("Retrying $indexStats aggregation on transient error", {error: e});
continue;
}
throw e;