[
https://issues.apache.org/jira/browse/AURORA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533281#comment-14533281
]
Meghdoot Bhattacharya commented on AURORA-1288:
-----------------------------------------------
Thx Brian for the pointers. We will do design code reviews when we start on it.
Bill, to run the state machine of the task in different states, do you rely
anything on the executor end. For example, when a job update is happening and
tasks are not deemed healthy under those timeouts, how much thermos executor is
playing the role for the scheduler to manage state. Because then custom
executors would need to mimic the same.
Some of the task tear down (/quitquitquit, /abortabortabort) on health ports
are thermos specific and can be skipped, but for health checks to manage the
task life cycle is there a dependency on the executor?. If UpdateConfig and
HealthChecker is purely managed on the scheduler end, I hope we are fine in
that case.
Thx
> Design for supporting custom executor
> -------------------------------------
>
> Key: AURORA-1288
> URL: https://issues.apache.org/jira/browse/AURORA-1288
> Project: Aurora
> Issue Type: Task
> Reporter: Meghdoot Bhattacharya
>
> The goal is to capture the list of changes in the client and the scheduler
> required to support any executor other than thermos. This will help non
> thermos use cases to adopt aurora easily.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
