[MESOS-7136] Eliminate fair sharing between frameworks within a role.

• Type: Epic
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Labels: multitenancy tech-debt
• Epic Name: Eliminate framework id acting as pseudo-role.
• Assignee: Unassigned
• Reporter: Benjamin Mahler
• Created: 16/Feb/17 21:47
• Updated: 27/Sep/17 16:34

Description

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:

                         ^
                       /   \
                  spark     services
                    ^
                  /   \
                /       \
    FrameworkId1         FrameworkId2
(fixed weight of 1)    (fixed weight of 1)

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.

                         ^
                       /   \
                    eng    sales
                    ^
                  /   \
         analytics     ui
             ^
           /   \
   learning     reports

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.

Issue Links

• is blocked by: MESOS-6375 Support hierarchical resource allocation roles.
• relates to: MESOS-6247 Enable Framework to set weight.