[jira] [Commented] (MESOS-1127) Implement the protobufs for the scheduler API

["Adam B (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14319390#comment-14319390 ] 

Adam B commented on MESOS-1127:
-------------------------------

I'm hoping we eventually get around to some awesome resource requests that allow us to take hints like "I'm Chronos, and I'm going to want a lot of resources at midnight". But I agree that we can add it later when needed.

For Registered/Reregistered, I'm considering using these messages in MESOS-2110 to pass the master's value for ping timeouts to the slave, so that it can disconnect/reregister at the right time, rather than having to guess. I suppose you can still remove the MasterInfo, but we may need to pass other data from master to slave on (re)registration.

> Implement the protobufs for the scheduler API
> ---------------------------------------------
>
>                 Key: MESOS-1127
>                 URL: https://issues.apache.org/jira/browse/MESOS-1127
>             Project: Mesos
>          Issue Type: Task
>          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
(v6.3.4#6332)