Use a timer instead of the system clock to detect pali progress timeout

ExportXMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.1.0-rc1023
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Fully Compatible
    • Repl 2026-09-28
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In BF-45929, we detected no progress immediately after becoming primary due to clock skew injected by nemesis. To make us more resilient to clock skew, use a timer instead of the system clock for this detection.

            Assignee:
            Indy Prentice
            Reporter:
            Indy Prentice
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: