[ 
https://issues.apache.org/jira/browse/MESOS-7136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975879#comment-15975879
 ] 

Benjamin Mahler commented on MESOS-7136:
----------------------------------------

[~qianzhang] yes, the plan would be to remove the special casing of framework 
id as a pseudo-role, so there would no longer be the additional sorters. To 
clarify what I meant by compete, the resources would be offered to all 
participants within a role and the first one to take it wins. If users wish to 
have constraints among frameworks using a role, they can use sub-roles 
identifying their frameworks, which achieves the existing behavior. But, you 
also get the added benefit of using actual roles, so you can change weights, 
set quota, etc.

> Eliminate fair sharing between frameworks within a role.
> --------------------------------------------------------
>
>                 Key: MESOS-7136
>                 URL: https://issues.apache.org/jira/browse/MESOS-7136
>             Project: Mesos
>          Issue Type: Epic
>          Components: allocation, technical debt
>            Reporter: Benjamin Mahler
>              Labels: multi-tenancy
>
> The current fair sharing algorithm performs fair sharing between frameworks 
> within a role. This is equivalent to having the framework id behave as a 
> pseudo-role beneath the role. Consider the case where there are two spark 
> frameworks running within the same "spark" role. This behaves similarly to 
> hierarchical roles with the framework ID acting as an implicit role:
> {noformat}
>                          ^
>                        /   \
>                   spark     services
>                     ^
>                   /   \
>                 /       \
>     FrameworkId1         FrameworkId2
> (fixed weight of 1)    (fixed weight of 1)
> {noformat}
> Unfortunately, the frameworks cannot change their weight to be a value other 
> than 1 (see MESOS-6247) and they cannot set quota.
> With the addition of hierarchical roles (see MESOS-6375) we can eliminate the 
> notion of the framework ID acting as a pseudo-role in favor of explicitly 
> using hierarchical roles. E.g.
> {noformat}
>                          ^
>                        /   \
>                     eng    sales
>                     ^
>                   /   \
>          analytics     ui
>              ^
>            /   \
>    learning     reports
> {noformat}
> Here if two frameworks run within the eng/analytics role, then they will 
> compete for resources without fair sharing. However, if resource guarantees 
> are required, sub-roles can be created explicitly, e.g. 
> eng/analytics/learning and eng/analytics/reports. These roles can be given 
> weights and quota.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to