dbcheck_no_history_on_secondary.js disables dbCheck failpoint too early

ExportXMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.4.15, 6.0.0-rc6, 5.0.10, 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v6.0, v5.0, v4.4
    • Execution Team 2022-05-16
    • 36
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This dbCheck depends on the primary acquiring a soon-to-be-stale snapshot for an error to be emitted in the secondary's health log collection. We can ensure that we reach the failpoint before starting to advance the durable timestamp using FailPoint.wait().

            Assignee:
            Benety Goh (Inactive)
            Reporter:
            Benety Goh (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: