mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yong Qiao Wang (JIRA)" <>
Subject [jira] [Commented] (MESOS-3177) Make Mesos own configuration of roles/weights
Date Thu, 17 Sep 2015 06:37:46 GMT


Yong Qiao Wang commented on MESOS-3177:

In addition, When we remove an existing role, we also need to call related slave to release
the resources which reserved by that role before. [~cmaloney], any thoughts for this? Thanks!

> Make Mesos own configuration of roles/weights
> ---------------------------------------------
>                 Key: MESOS-3177
>                 URL:
>             Project: Mesos
>          Issue Type: Improvement
>          Components: master, slave
>            Reporter: Cody Maloney
>            Assignee: Thomas Rampelberg
>              Labels: mesosphere
> All roles and weights must currently be specified up-front when starting Mesos masters
currently. In addition, they should be consistent on every master, otherwise unexpected behavior
could occur (You can have them be inconsistent for some upgrade paths / changing the set).
> This makes it hard to introduce new groups of machines under new roles dynamically (Have
to generate a new master configuration, deploy that, before we can connect slaves with a new
role to the cluster).
> Ideally an administrator can manually add / remove / edit roles and have the settings
replicated / passed to all masters in the cluster by Mesos. Effectively Mesos takes ownership
of the setting, rather than requiring it to be done externally.
> In addition, if a new slave joins the cluster with an unexpected / new role that should
just work, making it much easier to introduce machines with new roles. (Policy around whether
or not a slave can cause creation of a new role, a given slave can register with a given role,
etc. is out of scope, and would be controls in the general registration process).

This message was sent by Atlassian JIRA

View raw message