summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJason Chan <jason.chan@mongodb.com>2022-01-05 16:54:57 +0000
committerEvergreen Agent <no-reply@evergreen.mongodb.com>2022-01-05 17:53:15 +0000
commite2d48665f771a82bfe7de2a112276cd3692a6007 (patch)
treeb369fb3314d3d31323ccf919c67312b46a021109
parent619d0d3c24ca4b287098a343fb95c92e325c3d1b (diff)
downloadmongo-e2d48665f771a82bfe7de2a112276cd3692a6007.tar.gz
SERVER-61923 Fix bug where consistency checker can mask error due to ignoring inconsistency in image collections
-rw-r--r--src/mongo/shell/data_consistency_checker.js8
1 files changed, 7 insertions, 1 deletions
diff --git a/src/mongo/shell/data_consistency_checker.js b/src/mongo/shell/data_consistency_checker.js
index b0282603edf..9530b12c416 100644
--- a/src/mongo/shell/data_consistency_checker.js
+++ b/src/mongo/shell/data_consistency_checker.js
@@ -335,7 +335,13 @@ var {DataConsistencyChecker} = (function() {
collectionPrinted, sourceCollInfos, syncingCollInfos, collName);
const shouldIgnoreFailure =
this.canIgnoreCollectionDiff(sourceCollInfos, syncingCollInfos, collName);
- success = shouldIgnoreFailure;
+ if (shouldIgnoreFailure) {
+ prettyPrint(
+ `Collection diff in ${dbName}.${collName} can be ignored: ${dbHashesMsg}
+ . Inconsistencies in the image collection can be expected in certain
+ restart scenarios.`);
+ }
+ success = shouldIgnoreFailure && success;
}
});