progress_monitor_doesnt_crash_on_not_critical should use a smaller value of PROGRESS_TIMEOUT_SECONDS

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0, 6.0.17
    • Affects Version/s: None
    • Component/s: None
    • Cluster Scalability
    • Fully Compatible
    • v6.0
    • Cluster Scalability 2024-07-22
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      This is because if the progress monitor runs every 5 seconds (the interval specified in the test) and the liveness time it waits for is 5 seconds , it possible for it to take more time than the current time the test waits for (5.5 seconds) to fail.

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

              Created:
              Updated:
              Resolved: