[
https://issues.apache.org/jira/browse/MESOS-8167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16329794#comment-16329794
]
Greg Mann commented on MESOS-8167:
----------------------------------
Since this is a rather forward-looking epic, I thought I'd toss a couple
thoughts here regarding the long-term future of executors. In my mind, a better
option for the V2 API would be to make frameworks ignorant of executors
entirely. I'm not convinced that it's a useful abstraction at this point. I
would be curious how many users are currently running custom executors, for
example. The feedback I have gotten from framework devs in the past is that
custom executors are difficult to deal with, and we have added quite a bit of
functionality to the default executor in order to increase the breadth of use
cases it can satisfy.
Whenever we start exploring designs for the V2 API in earnest, I think we
should consider eliminating custom executors, and completely removing the
executor from the scheduler API. The logical units of work from the framework's
perspective are tasks and task groups. Unless there are real use cases which
cannot be served by exposing executor concepts in the API, I think it would
simplify the Mesos task lifecycle story and make it easier to develop
frameworks.
> Introduce an executor lifecycle API.
> ------------------------------------
>
> Key: MESOS-8167
> URL: https://issues.apache.org/jira/browse/MESOS-8167
> Project: Mesos
> Issue Type: Epic
> Components: scheduler api
> Reporter: Benjamin Mahler
> Priority: Major
>
> Much like agents and tasks, there is a need for schedulers to track the
> lifecycle of executors that they own (updates, reconciliation, health) as
> well.
> Schedulers can currently shut their executors down, but without having a
> lifecycle API to know when they are running, this isn't very useful.
> Part of this effort would include ensuring that the executors are correctly
> kept in sync across the master and agent: MESOS-1961.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
