Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Sat, 22 Jul 2017 01:06:00 +0000 (UTC)
From: "Benjamin Mahler (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.13064961.1492570907000.306979.1500685560291@Atlassian.JIRA>
In-Reply-To: <JIRA.13064961.1492570907000@Atlassian.JIRA>
References: <JIRA.13064961.1492570907000@Atlassian.JIRA> <JIRA.13064961.1492570907422@jira-lw-us.apache.org>
Subject: [jira] [Updated] (MESOS-7402) Allocated quota of a child role
 should be also charged on all ancestors of that role
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 22 Jul 2017 01:06:04 -0000


     [ https://issues.apache.org/jira/browse/MESOS-7402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Mahler updated MESOS-7402:
-----------------------------------
    Priority: Blocker  (was: Major)

> 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
>            Assignee: Jay Guo
>            Priority: Blocker
>              Labels: multitenancy
>         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.4.14#64029)