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

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

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.0.0-rc2, 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Fully Compatible
    • ALL
    • v5.0, v4.4, v4.2, v4.0

      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:
            jack.mulrow@mongodb.com Jack Mulrow
            Reporter:
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: