You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Kai Huang (JIRA)" <ji...@apache.org> on 2016/09/06 18:03:20 UTC

[jira] [Resolved] (AURORA-1223) Modify scheduler updater to not use "watch_secs" for health-check enabled jobs

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

Kai Huang resolved AURORA-1223.
-------------------------------
    Resolution: Fixed

After discussion on Aurora dev list, it turns out there will be no scheduler-side change associated with this issue.

Our final conclusion is that we adopt the following implementation:

If the users want purely health checking driven updates they can set watch_secs to 0 and enable health checks.  (watch_secs=0 is not allowed at client side, we will relax this constraint after we modified executor. However, no scheduler change is required since scheduler allows non-negative values for watch_secs)

If they want to have both health checking and time driven updates they can set watch_secs to the time that they care about, and doing health checks at STARTING state as well.

If they just want time driven updates they can disable health checking and set watch_secs to the time that they care about..

> Modify scheduler updater to not use "watch_secs" for health-check enabled jobs
> ------------------------------------------------------------------------------
>
>                 Key: AURORA-1223
>                 URL: https://issues.apache.org/jira/browse/AURORA-1223
>             Project: Aurora
>          Issue Type: Task
>          Components: Scheduler
>            Reporter: Maxim Khutornenko
>            Assignee: Kai Huang
>
> When health checks are enabled in a job config, scheduler updater should ignore "watch_secs" UpdateConfig value. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)