Details
-
Bug
-
Resolution: Fixed
-
Critical - P2
-
None
-
None
-
Fully Compatible
-
ALL
-
Repl 2021-01-25
Description
The changes from c1889f6 as part of SERVER-50935 allow success to transition from false back to true upon checking the dbhash of the subsequent database or subsequent secondary.
for (const dbName of combinedDBs) { |
...
|
dbHashes.secondaries.forEach(secondaryDBHash => {
|
...
|
print(
|
`checking db hash between primary: ${primary} and secondary ${secondary}`);
|
success = DataConsistencyChecker.checkDBHash(primaryDBHash,
|
primaryCollInfos,
|
secondaryDBHash,
|
secondaryCollInfos,
|
msgPrefix,
|
ignoreUUIDs,
|
hasSecondaryIndexes,
|
collectionPrinted);
|
...
|
});
|
}
|
|
|
assert(success, 'dbhash mismatch between primary and secondary'); |
I was seeing the following log message in a local resharding fuzzer run, but the test wasn't failing as a result.
[js_test:resharding_fuzzer-b3454-1610836920400-0] 2021-01-16T22:42:30.203+0000 checkReplicatedDataHashes, the two nodes have a different hash for the collection config.transactions: source: {
|
...
|
[executor:js_test:job0] 2021-01-16T22:43:40.920+0000 resharding_fuzzer-b3454-1610836920400-0.js ran in 85.50 seconds: no failures detected.
|
Attachments
Issue Links
- is caused by
-
SERVER-50935 Expand dbhash checks to ensure two replica sets are in sync for a given tenantId
-
- Closed
-
- is related to
-
SERVER-33068 run_check_repl_dbhash.js hook exits without actually running dbhash on a replica set
-
- Closed
-
-
SERVER-37197 Validation failure does not cause test to fail
-
- Closed
-
- related to
-
SERVER-53855 Resharding recipient secondaries ignore no-op oplog entries meant to bump config.transactions records
-
- Closed
-