The slave picks up total available resources (not free) on startup, but this can be overridden by the --resources="" flag. That way, you can leave resources for your out of bound processes.
If you want to compute the slack (difference between allocated and actually used), you can compute that from the slave's /monitor/statistics.json endpoint. You should be able to pick up some documentation on that endpoint from /help/monitor/statistics.json If you are looking for something more dynamic, you should follow the discussion on oversubscription :) Cheers, Niklas On 9 February 2015 at 02:34, craig w <codecr...@gmail.com> wrote: > Mesos slaves report the total resources they have available, such as 2 > CPU, 8GB Memory and 100GB disk. > > Does Mesos keep track of the amount of resources that are actually > available to best schedule tasks? > > For example, imagine a slave has some other processes running on it (that > are not mesos tasks) that are taking up 6GB of RAM (out of the total 8GB). > A new task is created in Mesos that needs 4GB of RAM, would Mesos still try > to put the new task on the slave? >
