Thanks Adam! It is clear to me now :-)
2015-06-12 7:49 GMT+08:00 Adam Bordelon <[email protected]>:
> 4. By default, Mesos will not revoke ("rescind") an *un*used offer being
> held by a framework, but you can enable such a timeout by specifying the
> `--offer_timeout` flag on the master.
>
> On Thu, Jun 11, 2015 at 4:48 PM, Adam Bordelon <[email protected]> wrote:
>
>> 1. The modularized allocator will still be a C++ interface, but you could
>> just create a C++ wrapper around whatever Python/Go/Java/etc.
>> implementation that you prefer.
>>
>> Your assessment of 2&3 sounds correct.
>>
>> 4. By default, Mesos will not revoke ("rescind") an used offer being held
>> by a framework, but you can enable such a timeout by specifying the
>> `--offer_timeout` flag on the master.
>>
>> On Thu, Jun 11, 2015 at 1:41 AM, baotiao <[email protected]> wrote:
>>
>>> Hi Qian Zhang
>>>
>>> I can answer the fourth question.
>>>
>>> if a framework has not responded to an offer for a sufficiently long
>>> time, Mesos rescinds the offer and re-offers the resources to other
>>> frameworks.
>>> You cant get it
>>>
>>> I am not clear in how Mesos divide all resources into multiple subsets?
>>>
>>> ----------------------------------------
>>> 陈宗志
>>>
>>> Blog: baotiao.github.io
>>>
>>>
>>>
>>>
>>> On Jun 11, 2015, at 08:35, Qian Zhang <[email protected]> wrote:
>>>
>>> Thanks Alex.
>>>
>>> For 1. I understand currently the only choice is C++. However, as Adam
>>> mentioned, true pluggable allocator modules (MESOS-2160
>>> <https://issues.apache.org/jira/browse/MESOS-2160>) are landing in
>>> Mesos 0.23, so at that time, I assume we will have more choices, right?
>>>
>>> For 2 and 3, my understanding is Mesos allocator will partition all the
>>> available resources into multiple subsets, and there is no overlap between
>>> these subsets (i.e., a single resource can only be in one subset), and then
>>> offer these subsets to multiple frameworks (e.g., offer subset1 to
>>> framework1, offer subset2 to framework2, and so on), and it is up to each
>>> framework's scheduler to determine if it accept the resource to launch task
>>> or reject it. In this way, each framework's scheduler can actually make
>>> scheduling decision independently since they will never compete for the
>>> same resource.
>>>
>>> If my understanding is correct, then I have one more question:
>>> 4. What if it takes very long time (e.g., mins or hours) for a
>>> framework's scheduler to make the scheduling decision? Does that mean
>>> during this long period, the resources offered to this framework will not
>>> be used by any other frameworks? Is there a timeout for the
>>> framework's scheduler to make the scheduling decision? So when the timeout
>>> is reached, the resources offered to it will be revoked by Mesos allocator
>>> and can be offered to another framework.
>>>
>>>
>>>
>>
>
