Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-53854

checkReplicatedDataHashes() may return without throwing despite detecting a dbhash mismatch

    • Fully Compatible
    • ALL
    • Repl 2021-01-25

      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.
      

            Assignee:
            xuerui.fa@mongodb.com Xuerui Fa
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: