[
https://issues.apache.org/jira/browse/MESOS-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16386958#comment-16386958
]
Klaus Ma commented on MESOS-4553:
---------------------------------
According to the previous comments, it's handled in -MESOS-3147- ; is that
correct? That'll be great if we can manage offer in allocator, it'll also give
more room for other to enhance allocator policy :)
> Manage offers in allocator.
> ---------------------------
>
> Key: MESOS-4553
> URL: https://issues.apache.org/jira/browse/MESOS-4553
> Project: Mesos
> Issue Type: Epic
> Components: master
> Reporter: Klaus Ma
> Assignee: Joseph Wu
> Priority: Major
> Labels: multitenancy
>
> Currently, Offers are managed by {{Master}} while Resources are handled by
> the {{Allocator}}. This introduces a variety of races between the {{Master}}
> and {{Allocator}} actors; and limitations with regards to information that
> the {{Allocator}} can act upon. See the linked issues for some examples of
> races/limitations.
> The goal of this epic is to track a refactor of the {{Master}} and
> {{Allocator}}. The {{Master}} should continue to manage communication with
> {{Frameworks}}, including the act of sending Offers, but all state associated
> with Offers (primarily OfferIDs and Timers), will be off-loaded to the
> {{Allocator}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)