mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joseph Wu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-3043) Master does not handle InverseOffers in the Accept call (Event/Call API)
Date Tue, 14 Jul 2015 22:51:05 GMT

     [ https://issues.apache.org/jira/browse/MESOS-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Joseph Wu updated MESOS-3043:
-----------------------------
    Summary: Master does not handle InverseOffers in the Accept call (Event/Call API)  (was:
Master should handle InverseOffers in the Accept call (Event/Call API))

> Master does not handle InverseOffers in the Accept call (Event/Call API)
> ------------------------------------------------------------------------
>
>                 Key: MESOS-3043
>                 URL: https://issues.apache.org/jira/browse/MESOS-3043
>             Project: Mesos
>          Issue Type: Task
>          Components: master
>            Reporter: Joseph Wu
>              Labels: mesosphere
>
> InverseOffers are similar to Offers in that they are Accepted or Declined based on their
OfferID.  
> Some additional logic may be neccesary in Master::accept (src/master/master.cpp) to gracefully
handle the acceptance of InverseOffers.
> * The InverseOffer needs to be removed from the set of pending InverseOffers.
> * The InverseOffer should not result any errors/warnings.  
> Note: accepted InverseOffers do not preclude further InverseOffers from being sent to
the framework.  Instead, an accepted InverseOffer merely signifies that the framework is _currently_
fine with the expected downtime.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message