mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominic Hamon (JIRA)" <>
Subject [jira] [Updated] (MESOS-1127) Expose lower-level scheduler/executor API
Date Mon, 26 Jan 2015 19:48:34 GMT


Dominic Hamon updated MESOS-1127:
    Epic Name: HTTP API

> Expose lower-level scheduler/executor API
> -----------------------------------------
>                 Key: MESOS-1127
>                 URL:
>             Project: Mesos
>          Issue Type: Epic
>          Components: framework
>            Reporter: Benjamin Hindman
>            Assignee: Benjamin Hindman
>              Labels: twitter
> 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

View raw message