My bad, Seeing the 1002mb(~1024) number made me think the agent was not able to get the memory estimates from the OS and defaulting to the constant values.
The slave executes a `sysinfo` system call and populates the memory numbers based on it. If you want a more fine-grained control, try to specify it directly using the —resources flag as I had mentioned earlier. -anand > On Sep 2, 2015, at 6:48 PM, F21 <[email protected]> wrote: > > There seems to be some dynamicness to it. I just bumped the memory for each > VM up to 2.5GB and now mesos is offering 1.5GB on it's slave. Is there some > percentage value that I can set so that more memory is available to mesos? > > On 3/09/2015 11:23 AM, Anand Mazumdar wrote: >> In case you don’t specify the resources via “—resources” flag when you start >> your agent, it picks up the default values. (Example: >> --resources="cpus:4;mem:1024;disk:20000”) >> >> The default value for memory is here: >> <https://github.com/apache/mesos/blob/master/src/slave/constants.cpp#L46>https://github.com/apache/mesos/blob/master/src/slave/constants.cpp#L46 >> <https://github.com/apache/mesos/blob/master/src/slave/constants.cpp#L46> >> >> -anand >>
