[
https://issues.apache.org/jira/browse/MESOS-7136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975911#comment-15975911
]
Qian Zhang edited comment on MESOS-7136 at 4/20/17 3:03 AM:
------------------------------------------------------------
{quote}
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
{quote}
[~bmahler] Without framework sorter, for multiple frameworks in the same role
but no sub-roles created for them, how are we going to figure out which
framework in that role is the first one? Or we want to implicitly create a leaf
role for the framework when it subscribes to master so that the role sorter can
handle all the roles and frameworks in a consistent way?
was (Author: qianzhang):
{quote}
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
{quote}
Without framework sorter, for multiple frameworks in the same role but no
sub-roles created for them, how are we going to figure out which framework in
that role is the first one?
> 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)
