Thanks!
Le ven. 1 mai 2020 à 00:11, Vinod Kone a écrit :
>
> I commented on the JIRA.
>
> On Thu, Apr 30, 2020 at 3:02 PM Charles-François Natali
> wrote:
>
> > Thanks Vinod.
> >
> > Yes, I understand that Mesos assumes it's the only process managing
> > resources, makes sense.
> > Looking at th
I commented on the JIRA.
On Thu, Apr 30, 2020 at 3:02 PM Charles-François Natali
wrote:
> Thanks Vinod.
>
> Yes, I understand that Mesos assumes it's the only process managing
> resources, makes sense.
> Looking at the code and testing shows the agent reports as available
> memory the total memo
Thanks Vinod.
Yes, I understand that Mesos assumes it's the only process managing
resources, makes sense.
Looking at the code and testing shows the agent reports as available
memory the total memory of the host, minus 1GB (or half the total
memory if the total memory is below 2GB)
(https://github.
Mesos assumes that it is the only process managing resources of a box (cpu,
mem, disk). So if you have out of band processes using up resources it
won't be reflected in the resource offers and the box can be overcommitted.
There is no runtime periodic check of available resources, it's only
calcula
Hi,
Could someone point me to some code/documentation explaining how the
agent available memory is computed, and when it is refreshed?
For example, if I have an agent started, with some outstanding offers,
and I then start a process - not as a task managed by Mesos, but as an
external process whi
