mesos-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benjamin Staffin <>
Subject Re: Mesos Slave gets registered with lower memory than available
Date Tue, 21 Oct 2014 13:04:36 GMT
Related to this, is there a good way to set resource limits for the system
running outside of mesos? It would be great if I could put a hard limit on
memory usage for non-containerized processes (sshd, upstart, mesos-slave
itself, chef, admin shell sessions, the docker daemon, etc) to make way for
tighter binpacking of resources.
On Oct 1, 2014 10:11 AM, "Vinod Kone" <> wrote:

> Stefan, mind filing a ticket <http://VirtualChannel> about the
> documentation gap?
> On Wed, Oct 1, 2014 at 9:27 AM, Tim Chen <> wrote:
>> Hi Stefan,
>> Yes it's a feature where we leave some space on each slave and not fully
>> allocate all the memory and cpu.
>> You can override how much resource your slave advertises by passing in
>> the --resources flag when you start your slave.
>> Tim
>> On Wed, Oct 1, 2014 at 9:22 AM, Stefan Eder <> wrote:
>>> Hi,
>>> I'm relatively new to Mesos and trying to setup a cluster for Jenkins
>>> slaves. Currently I have three machines running master, slave and
>>> zookeepers and one only running a slave.
>>> Everything works fine so far, except that the slaves registered on the
>>> master have a lover memory value than available on the machine. For
>>> example if I use a computer with 8GB then the registered value of that
>>> slave will be around 6.7GB. So there are around 1.3GB which are
>>> "missing".
>>> I guess that this is a feature and not a bug (probably to ensure that
>>> other processes and what not can also run on the machine). However, is
>>> there a way to decrease that value?
>>> So far I found nothing about this in the documentation or elsewhere. Am
>>> I missing something?
>>> Would be nice if someone could help me.
>>> Thanks,
>>> Stefan

View raw message