[jira] [Updated] (MESOS-2018) Dynamic Reservations
[ 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. 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/lazily 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. > Dynamic Reservations > > > 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: 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2018) Dynamic Reservations
[ https://issues.apache.org/jira/browse/MESOS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niklas Quarfot Nielsen updated MESOS-2018: -- Sprint: Mesosphere Q4 Sprint 2 - 11/14, Mesosphere Q4 Sprint 3 - 12/7, Mesosphere Q1 Sprint 1 - 1/23, Mesosphere Q1 Sprint 2 - 2/6 (was: Mesosphere Q4 Sprint 2 - 11/14, Mesosphere Q4 Sprint 3 - 12/7, Mesosphere Q1 Sprint 1 - 1/23) > Dynamic Reservations > > > 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: 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, 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2018) Dynamic Reservations
[ https://issues.apache.org/jira/browse/MESOS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niklas Quarfot Nielsen updated MESOS-2018: -- Sprint: Mesosphere Q4 Sprint 2 - 11/14, Mesosphere Q4 Sprint 3 - 12/7, Mesosphere Sprint 4 - 1/23/15 (was: Mesosphere Q4 Sprint 2 - 11/14, Mesosphere Q4 Sprint 3 - 12/7) > Dynamic Reservations > > > 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: 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, 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2018) Dynamic Reservations
[ https://issues.apache.org/jira/browse/MESOS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niklas Quarfot Nielsen updated MESOS-2018: -- Sprint: Mesosphere Q4 Sprint 2 - 11/14, Mesosphere Q4 Sprint 3 - 11/30 (was: Mesosphere Q4 Sprint 2 - 11/14) > Dynamic Reservations > > > 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: 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, 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2018) Dynamic Reservations
[ 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/lazily 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. 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/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. > Dynamic Reservations > > > 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: 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, 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-2018) Dynamic Reservations
[ https://issues.apache.org/jira/browse/MESOS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Park updated MESOS-2018: Epic Name: Dynamic Reservations (was: Dynamic Resource Reservations) Summary: Dynamic Reservations (was: Dynamic Resource Reservations) > Dynamic Reservations > > > 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: 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)
