Cluster time keys refresh interval doesn't back off on consecutive errors

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Sharding NYC
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When refreshing cluster time keys, if an error occurs, the next refresh is meant to happen in 200ms * the number of consecutive errors, with a max interval of 10 minutes. The error count is set to 0 at the beginning of the while loop where retries happen though, so it can never be greater than 1, meaning the intended back off logic never applies and the interval is always 200ms.

            Assignee:
            [DO NOT USE] Backlog - Sharding NYC
            Reporter:
            Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: