You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Dominic Hamon (JIRA)" <ji...@apache.org> on 2015/01/22 19:46:34 UTC
[jira] [Updated] (MESOS-1127) Expose lower-level scheduler/executor
API
[ https://issues.apache.org/jira/browse/MESOS-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dominic Hamon updated MESOS-1127:
---------------------------------
Issue Type: Epic (was: Improvement)
> Expose lower-level scheduler/executor API
> -----------------------------------------
>
> Key: MESOS-1127
> URL: https://issues.apache.org/jira/browse/MESOS-1127
> Project: Mesos
> Issue Type: Epic
> Components: framework
> Reporter: Benjamin Hindman
> Assignee: Benjamin Hindman
>
> The default scheduler/executor interface and implementation in Mesos have a few drawbacks:
> (1) The interface is fairly high-level which makes it hard to do certain things, for example, handle events (callbacks) in batch. This can have a big impact on the performance of schedulers (for example, writing task updates that need to be persisted).
> (2) The implementation requires writing a lot of boilerplate JNI and native Python wrappers when adding additional API components.
> The plan is to provide a lower-level API that can easily be used to implement the higher-level API that is currently provided. This will also open the door to more easily building native-language Mesos libraries (i.e., not needing the C++ shim layer) and building new higher-level abstractions on top of the lower-level API.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)