[
https://issues.apache.org/jira/browse/MESOS-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743664#comment-14743664
]
haosdent commented on MESOS-2064:
---------------------------------
In this discussion, we suggest to support InverseOffer through V1 API in java.
[Do we still need to add InverseOffer support to Scheduler
API|http://search-hadoop.com/m/0Vlr6EWNESWcZkd1]
> Add InverseOffer to Java Scheduler API.
> ---------------------------------------
>
> Key: MESOS-2064
> URL: https://issues.apache.org/jira/browse/MESOS-2064
> Project: Mesos
> Issue Type: Task
> Components: java api
> Reporter: Benjamin Mahler
> Assignee: Yong Qiao Wang
> Labels: mesosphere, twitter
>
> The initial use case for InverseOffer in the framework API will be the
> maintenance primitives in mesos: MESOS-1474.
> One way to add these to the Java Scheduler API is to add a new callback:
> {code}
> void inverseResourceOffers(
> SchedulerDriver driver,
> List<InverseOffer> inverseOffers);
> {code}
> JAR / libmesos compatibility will need to be figured out here.
> We may want to leave the Java binding untouched in favor of Event/Call, in
> order to not break API compatibility for schedulers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
