[jira] [Updated] (MESOS-2318) Ability to modify / bias max shares at runtime

["Vinod Kone (JIRA)" <ji...@apache.org>]

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

Vinod Kone updated MESOS-2318:
------------------------------
    Affects Version/s:     (was: 0.21.1)
           Issue Type: Task  (was: Bug)

What does it mean to bias max shares? Max shares are calculated based on the resources allocated to a framework. Do you mean to change the max share values irrespective of the allocations? That seems unintuitive?

> Ability to modify / bias max shares at runtime
> ----------------------------------------------
>
>                 Key: MESOS-2318
>                 URL: https://issues.apache.org/jira/browse/MESOS-2318
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Cody Maloney
>
> When running multiple frameworks on a cluster, some frameworks are frequently "big" (Marathon, Aurora) and should be able to get most of the cluster while other frameworks use small amounts of the resources (Just 3 nodes for HA, just launching one or two things on demand).
> I don't know my workload / cluster is going to get into this shape until it is up and running, so doing restarts all around to configure in roles, or bias the shares is less than ideal. It really needs to be able to be managed at runtime in mesos.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)