Benjamin Mahler created MESOS-6375:
--------------------------------------
Summary: Support hierarchical resource allocation roles.
Key: MESOS-6375
URL: https://issues.apache.org/jira/browse/MESOS-6375
Project: Mesos
Issue Type: Epic
Components: allocation
Reporter: Benjamin Mahler
Currently mesos provides a non-hierarchical resource allocation model, in which
all roles are siblings of one another.
Organizations often have a need for hierarchical resource allocation
constraints, whether for fair sharing of resources or for specifying quota
constraints.
Consider the following fair sharing hierarchy based on "shares":
{noformat}
^ ^
/ \ / \
/ \ / \
eng (3) sales (1) => eng (75%) sales (25%)
^ ^
/ \ / \
/ \ / \
ads (2) build (1) ads (66%) build (33%)
{noformat}
The hierarchy specifies that the engineering organization should get 3x as many
resources as sales, and within these resources the ads team should get 2x as
many resources as the build team. The implication of this is that, if the ads
team is not using some of its resources, the build team and engineering
organization will be able to use these resources before the sales organization
can. Without a hierarchy, the resources unused by the ads team would be
re-distributed among all other roles (rather than only its siblings).
Quota can also apply in a hierarchical manner:
{noformat}
^
/ \
/ \
eng (90 cpus) sales (10 cpus)
^
/ \
/ \
ads (50 cpus) build (10 cpus)
{noformat}
See https://people.eecs.berkeley.edu/~alig/papers/h-drf.pdf for some discussion
w.r.t. sharing resources in a hierarchical model.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
