You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@aurora.apache.org by "Maxim Khutornenko (JIRA)" <ji...@apache.org> on 2014/05/28 03:08:01 UTC

[jira] [Updated] (AURORA-479) Drop restart_threshold > watch_secs validation in UpdateConfig

     [ https://issues.apache.org/jira/browse/AURORA-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maxim Khutornenko updated AURORA-479:
-------------------------------------

    Sprint: Q2 Sprint 2

> Drop restart_threshold > watch_secs validation in UpdateConfig
> --------------------------------------------------------------
>
>                 Key: AURORA-479
>                 URL: https://issues.apache.org/jira/browse/AURORA-479
>             Project: Aurora
>          Issue Type: Task
>          Components: Client
>            Reporter: Maxim Khutornenko
>            Assignee: Maxim Khutornenko
>
> 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).



--
This message was sent by Atlassian JIRA
(v6.2#6252)