Uploaded image for project: 'Aurora'
  1. Aurora
  2. AURORA-479

Drop restart_threshold > watch_secs validation in UpdateConfig

    XMLWordPrintableJSON

Details

    • Task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 0.5.0
    • Client
    • None
    • Q2 Sprint 2

    Description

      The "restart_threshold > watch_secs" validation introduced as a part of AURORA-404 is not necessary. While having an elevated restart_threshold value for a larger service is logical, having it tied to watch_secs is not. A counter example could be a CPU-demanding service that takes just a few seconds to become healthy (low watch_secs) but takes long(er) to get scheduled (restart_threshold).

      Attachments

        Activity

          People

            maximk Maxim Khutornenko
            maximk Maxim Khutornenko
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: