[
https://issues.apache.org/jira/browse/MESOS-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15049080#comment-15049080
]
Neil Conway commented on MESOS-4102:
------------------------------------
Thanks for the explanation. I understand what is going on, so the question is
whether this is the best behavior. Basically, the current implementation of
event-triggered allocations will always make legal allocations (per quota), but
might not make all the allocations that legally could be made. Is that
considered a problem and/or something we want to change?
It would be helpful for me to understand why we have event-triggered
allocations in the first place. If we need regular batch allocations to ensure
that all resources are allocated appropriately, then I guess event-triggered
allocations are just intended to be a "best-effort" mechanism, to do
_something_ about a change in cluster state until the next batch allocation
occurs?
> Quota doesn't allocate resources on slave joining
> -------------------------------------------------
>
> Key: MESOS-4102
> URL: https://issues.apache.org/jira/browse/MESOS-4102
> Project: Mesos
> Issue Type: Bug
> Components: allocation
> Reporter: Neil Conway
> Labels: mesosphere, quota
> Attachments: quota_absent_framework_test-1.patch
>
>
> See attached patch. {{framework1}} is not allocated any resources, despite
> the fact that the resources on {{agent2}} can safely be allocated to it
> without risk of violating {{quota1}}. If I understand the intended quota
> behavior correctly, this doesn't seem intended.
> Note that if the framework is added _after_ the slaves are added, the
> resources on {{agent2}} are allocated to {{framework1}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
