mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam B (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (MESOS-2018) Dynamic Resource Reservations
Date Fri, 31 Oct 2014 00:58:34 GMT

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

Adam B reassigned MESOS-2018:
-----------------------------

    Assignee: Adam B  (was: Michael Park)

> Dynamic Resource Reservations
> -----------------------------
>
>                 Key: MESOS-2018
>                 URL: https://issues.apache.org/jira/browse/MESOS-2018
>             Project: Mesos
>          Issue Type: Improvement
>          Components: allocation, framework, master, slave
>            Reporter: Adam B
>            Assignee: Adam B
>              Labels: offer, persistence, reservations, resource, stateful, storage
>
> This is a feature to provide better support for running stateful services on Mesos such
as HDFS (Distributed Filesystem), Cassandra (Distributed Database), or MySQL (Local Database).
> Current resource reservations (henceforth called "static" reservations) are statically
determined by the slave operator at slave start time, and individual frameworks have no authority
to reserve resources themselves.
> Dynamic reservations allow a framework to dynamically/lazily reserve offered resources
at task launch time, such that when that task completes, those resources will only be re-offered
to the same framework (or other frameworks with the same role).
> This is especially useful if the framework's task stored some state on the slave, and
needs a guaranteed set of resources reserved so that it can re-launch a task on the same slave
to recover that state.



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

Mime
View raw message