dbcheck_detects_data_corruption.js needs to wait for primary to log healthlog entry

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.1.0-rc0, 7.0.1
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • ALL
    • v7.0, v6.0
    • Execution Team 2023-05-29
    • 14
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The test waits for the secondary to log the "dbCheckStop" entry, but that is not enough to guarantee that the primary has logged its entry. This is because health log entries are written asynchronously with replicating the oplog entries.

      On slow machines, it could be possible to replicate the dbCheckStop oplog entry and have the secondary write to its healthlog before the primary.

              Assignee:
              Louis Williams
              Reporter:
              Louis Williams
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: