[
https://issues.apache.org/jira/browse/MESOS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Park updated MESOS-2018:
--------------------------------
Description:
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 reserve offered
resources, such that 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.
h3. Planned Stages
1. MESOS-2489: Enable a framework to perform reservation operations.
The goal of this stage is to allow the framework to send back a
Reserve/Unreserve operation which gets validated by the master and updates the
allocator resources. The allocator's {{allocate}} logic is unchanged and
therefore the resources get offered back to the framework's role rather than
the specific framework. In the next stage, we'll teach the allocator to
distinguish between role and framework reservations which will result in the
resources being re-offered to the specific framework.
2. MESOS-2490: Enable the allocator to distinguish between role and framework
reservations.
The goal of this stage of is to teach the allocator to offer resources reserved
for a framework to only be sent to the particular framework rather than the
framework's role. This will involve updating the {{allocate}} function to
select only the resources that are unreserved, role-reserved for the
framework's role and framework-reserved for the framework.
3.
was:
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 reserve offered
resources, such that 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.
h3. Planned Stages
[MESOS-2489|
> Dynamic Reservation
> -------------------
>
> Key: MESOS-2018
> URL: https://issues.apache.org/jira/browse/MESOS-2018
> Project: Mesos
> Issue Type: Epic
> Components: allocation, framework, master, slave
> Reporter: Adam B
> Assignee: Michael Park
> Labels: mesosphere, 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 reserve offered
> resources, such that 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.
> h3. Planned Stages
> 1. MESOS-2489: Enable a framework to perform reservation operations.
> The goal of this stage is to allow the framework to send back a
> Reserve/Unreserve operation which gets validated by the master and updates
> the allocator resources. The allocator's {{allocate}} logic is unchanged and
> therefore the resources get offered back to the framework's role rather than
> the specific framework. In the next stage, we'll teach the allocator to
> distinguish between role and framework reservations which will result in the
> resources being re-offered to the specific framework.
> 2. MESOS-2490: Enable the allocator to distinguish between role and framework
> reservations.
> The goal of this stage of is to teach the allocator to offer resources
> reserved for a framework to only be sent to the particular framework rather
> than the framework's role. This will involve updating the {{allocate}}
> function to select only the resources that are unreserved, role-reserved for
> the framework's role and framework-reserved for the framework.
> 3.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
