[
https://issues.apache.org/jira/browse/MESOS-7402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976812#comment-15976812
]
Jay Guo commented on MESOS-7402:
--------------------------------
[~qianzhang] yes, I think that could be a solution, ideally we could have a
tree structure in both master, sorter and allocator, and maybe sorter should be
quota-aware. I logged a JIRA for this: MESOS-7293
> Allocated quota of a child role should be also charged on all ancestors of
> that role
> ------------------------------------------------------------------------------------
>
> Key: MESOS-7402
> URL: https://issues.apache.org/jira/browse/MESOS-7402
> Project: Mesos
> Issue Type: Bug
> Reporter: Jay Guo
> Attachments: hrole_quota_test.patch
>
>
> Consider following case: role {{a}} is quota'd with resource 100, role
> {{a/b}} is quota'd with resource 40. In current implementation, quota of
> parent role is actually the aggregation of quota in whole subtree, including
> itself. Therefore, the internal node of {{a}} is actually quota'd with 60,
> instead of 100. In another word, allocation made for quota of {{a/b}} should
> also be charged from the quota of its parent.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
