[
https://issues.apache.org/jira/browse/MESOS-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738591#comment-14738591
]
Liqiang Lin commented on MESOS-3147:
------------------------------------
I think the current default Mesos allocator actually did not care about the
real resource usage of each framework, it only cares about "allocated" resource
which includes both framework used and offered resources. In the case, Mesos
allocator integrates with other third party scheduler (e.g., Yarn) which only
records the used resource, it's difficult to let the third party scheduler make
decision how many resource is used when framework launched tasks with offer.
Because current Mesos allocator did not have the info of framework used
resource. Only with one allocator interface recoverResource() and unused
resource as parameter, it's impossible to get the used resource of framework.
For this issue, does it make sense to add callback in allocator to get
framework used resource? Any other suggestions?
> Allocator refactor
> ------------------
>
> Key: MESOS-3147
> URL: https://issues.apache.org/jira/browse/MESOS-3147
> Project: Mesos
> Issue Type: Task
> Components: allocation, master
> Reporter: Michael Park
> Assignee: Guangya Liu
> Labels: mesosphere, tech-debt
>
> With new features such as dynamic reservation, persistent volume, quota,
> optimistic offers, it has been apparent that we need to refactor the
> allocator to
> 1. solidify the API (e.g. consolidate {{updateSlave}} and {{updateAvailable}})
> 2. possibly move the offer generation to the allocator from the master
> 3. support for allocator modules where the API involves returning
> {{libprocess::Future}}
> The sequence of implementation challenges for dynamic reservation master
> endpoints are captured in [this
> document|https://docs.google.com/document/d/1cwVz4aKiCYP9Y4MOwHYZkyaiuEv7fArCye-vPvB2lAI/edit?usp=sharing].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
