You set it up with 2048MB but you probably don't really get all of it (try
`free -m` on the slave). Same with Disk (look at the value of df).
from the book "Building Applications in Mesos":
"The slave will reserve 1 GB or 50% of detected memory, whichever is
smaller, in order to run itself and oth
ple, you might need a dns resolver, ntp, postfix, sshd, etc.
>> All of these services may need disk space for logging or other uses.
>>
>> On Tue, Mar 15, 2016 at 11:12 AM, Arkal Arjun Rao wrote:
>>
>>> Hi All,
>>>
>>> I read this line in the book &
Hi All,
I read this line in the book "Building Applications on Mesos - David
Greenberg":
" The slave will reserve 1 GB or 50% of detected memory, whichever
is smaller, in order to run itself and other operating system services.
Likewise, it will reserve 5 GB or 50% of detected disk, whichever is
cpu but not
> so much for disk.
>
> Mesos slave overcommits the disk in that sense. Mainly to allow task
> owners access to sandbox data after task termination. The asynchronous gc
> thread garbage collects the sandbox if there is disk space pressure on the
> host.
>
>
> @v
the finished task.
>
> Thanks!
>
>
>
> *From:* Arkal Arjun Rao [mailto:aa...@ucsc.edu]
> *Sent:* Friday, February 12, 2016 4:22 PM
> *To:* user@mesos.apache.org
> *Subject:* Re: Updated agent resources with every offer.
>
>
>
> Hi Vinod,
>
>
>
> Thanks fo
wrote:
> If your job is writing stuff outside the sandbox it is up to your
> framework to do that resource accounting. It is really tricky for Mesos to
> do that. For example, the second job might be launched even before the
> first one finishes.
>
> On Fri, Feb 12, 2016 at 3:46 PM,
Hi All,
I'm new to Mesos and I'm working on a framework that strongly considers
the disk value in an offer before making a decision. My jobs don't run in
the agent's sandbox and may use docker to pull images from my dockerhub and
run containers on input data downloaded from S3.
My jobs clean up
7 matches
Mail list logo
