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/07 16:52:20 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=15471115#comment-15471115 ]
Kai Huang commented on AURORA-1225:
-----------------------------------
Currently, aurora_executor sends the task status update to scheduler whereas the health checker performs the health check. When a successful required number of health checks is reached, the task state transitions to RUNNING. Therefore, the health checker needs to notify the aurora_executor about the state change. To solve this problem, we can implement a event-listener in aurora executor that listens to a "TASK_RUNNING_TRANSITION" event dispatched by health checker. Here is an example for the implementation of event dispatcher and event listener: http://code.activestate.com/recipes/577432-simple-event-dispatcher/
> 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
> Assignee: Kai Huang
>
> 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)