The resource over-subscription in a platform like Mesos is the thing that I
am also interested in. Looking forward to seeing progresses for the feature
- I will also update from my-side if I can observe something interesting.
thx.
On Mon, Nov 25, 2013 at 5:00 PM, Benjamin Mahler
wrote:
> In the
In the longer term, utilization will be improved through "oversubscription"
of the slave's resources. This means, giving out resources inside existing
resource allocations if they remain unused. These "over-subscribed"
resources would be revokable at any time.
On Mon, Nov 25, 2013 at 12:29 PM, ri
Thanks, Vinod. From the system utilization perspective, it might not be a
good idea to run a long-running service job (with sporadic workloads) that
might reserve a large portion of resources.
For the new feature, It seems like to deal with a case when a framework is
taking long to make accept/decl
Your understanding is correct. Currently, if a framework holds on to an
offer then it might impact other frameworks. If you want to guarantee that
each of your frameworks can receive certain amount of resources, you could
"reserve" resources to frameworks (roles). See the "--resources" flag on
the
hi,
I have a question about mesos behavior when a long running service job
(such as web-server or traditional RDBMS) accepts offers and run for a long
period of time with sporadic resource usage. Assuming that a long running
job gets assigned 30% of total available resources, I think Mesos will
as
5 matches
Mail list logo
