[
https://issues.apache.org/jira/browse/MESOS-7402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neil Conway updated MESOS-7402:
-------------------------------
Attachment: hrole_quota_test.patch
Attached is a test case for this problem (originally by Jay, a few minor tweaks
by me).
I agree that this is a legitimate problem.
I'm not sure if there is an easy way to fix it, short of implementing
full-blown support for hierarchical quota (e.g., quota delegation).
For Mesos 1.3.0, we might consider disallowing quota to be set on hierarchical
roles. i.e., quota could still be set on top-level roles, but not on a nested
role. Then when we implement proper quota delegation, this bug would naturally
be fixed as part of that effort.
> 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)
