You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Stephan Erb (JIRA)" <ji...@apache.org> on 2015/04/12 19:09:12 UTC
[jira] [Commented] (AURORA-1225) Modify executor state transition
logic to rely on health checks (if enabled)
[ https://issues.apache.org/jira/browse/AURORA-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14491588#comment-14491588 ]
Stephan Erb commented on AURORA-1225:
-------------------------------------
We also have to think about the meaning of initial_interval_secs. In its current form, health checks only start when the initial delay has passed. Commonly this delay has to be set very high in order to guarantee that a task will come up even in a worst case scenario (e.g., server where I pull my binary from is slow today).
I'd propose that we change the meaning of initial_interval_secs to: always send health checks but to ignore errors.
> Modify executor state transition logic to rely on health checks (if enabled)
> ----------------------------------------------------------------------------
>
> Key: AURORA-1225
> URL: https://issues.apache.org/jira/browse/AURORA-1225
> Project: Aurora
> Issue Type: Task
> Components: Executor
> Reporter: Maxim Khutornenko
>
> Executor needs to start executing user content in STARTING and transition to RUNNING when a successful required number of health checks is reached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)