Increase the number of oplog entries dumped in `ReplSetTest.checkReplicatedDataHashes`'s `checkDBHashesForReplset`

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.0.0-rc1
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Fully Compatible
    • ALL
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, if we find a data inconsistency in this method, we dump the latest 100 oplog entries.
      For BF-43511, this was insufficient and the critically relevant time range was outside of this window.
      This 100-entry value should be increased, I suggest to 1000 oplog entries.

      /** https://github.com/10gen/mongo/blob/5ce698e22b69702aa9cff9f0fcca904ea2a21476/jstests/libs/replsettest.js#L2966-L2977 */
      if (!success) {
        if (!hasDumpedOplog) {
          jsTest.log.info(
              "checkDBHashesForReplSet dumping oplogs from all nodes",
              );
          this.dumpOplog(primary, {}, 100);
          rst.getSecondaries().forEach((secondary) =>
              this.dumpOplog(secondary, {}, 100),
              );
          hasDumpedOplog = true;
        }
      

            Assignee:
            Joseph Obaraye
            Reporter:
            Joseph Obaraye
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: