Mathieu Velten created MESOS-2453:
-------------------------------------
Summary: [RFC] Auto scaling in Mesos
Key: MESOS-2453
URL: https://issues.apache.org/jira/browse/MESOS-2453
Project: Mesos
Issue Type: Improvement
Reporter: Mathieu Velten
Priority: Minor
Hi,
I am currently working for a project and we would like to use Mesos over a
classical IaaS.
After playing with Mesos and looking at some code it appears to me that there
is no elasticity mechanism in place, and I didn't find a JIRA entry regarding
this problem.
Here is what I have in mind :
Add the possibility for a framework to signal that it has some work pending
(with or without further semantics regarding what resources is wished ?)
Modify the mesos algo to call a pluggable driver when no resource is available
and at least one framework has some work to do.
In this case the driver should scale up the mesos cluster by launching VMs. How
much and of which size is a little tricky here without adding semantics to the
framework signal.
We should also add a flag somewhere to mark the slave as "volatile" so we can
prefer the use of static resources, and shut down the volatile slaves after
some time left unused.
Does it look doable to you ? what do you think about the principle ?
Do you think we can add some semantics to the "I have work to do" framework
signal without breaking the two-level scheduling principle ?
I don't think it violates it since both mechanisms (signalling a need and
effectively take a resource from an offer) are fully independent in my proposal
but I feel a little out of my league to be sure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
