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

dbcheck_no_history_on_secondary.js disables dbCheck failpoint too early

XMLWordPrintableJSON

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

      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@mongodb.com Benety Goh
            Reporter:
            benety.goh@mongodb.com Benety Goh
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: