[
https://issues.apache.org/jira/browse/MESOS-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Mahler updated MESOS-458:
----------------------------------
Description:
We currently have the following layout when there is no system cgroup present
on a machine:
/cgroup: (system processes, including the mesos-slave) 1024 shares
/cgroup/mesos: (no processes) 1024 shares
/cgroup/mesos/executor1: X shares
...
/cgroup/mesos/executorN: X shares
This does not ensure the slave gets a fair share of the cpu, especially when
there is load inside the root cgroup. This is because the slave is contending
with other processes inside the root cgroup. If the administrators set up a
system cgroup, the layout looks as follows:
/cgroup: (no processes)
/cgroup/system: (system processes, including the mesos-slave) 1024 shares
/cgroup/mesos: (no processes) 1024 shares
/cgroup/mesos/executor1: X shares
...
/cgroup/mesos/executorN: X shares
This still does not ensure the slave gets a fair share for the same reasons.
However, if we create a cgroup to hold only the slave:
/cgroup: (no processes)
/cgroup/system: (system processes) 1024 shares
/cgroup/mesos-slave: (mesos-slave process) 1024 shares
/cgroup/mesos: (no processes) 1024 shares
/cgroup/mesos/executor1: X shares
...
/cgroup/mesos/executorN: X shares
With the above configuration, the slave will get 1024 / (1024 + 1024 + 1024) =
1/3 of the CPUs, system processes will similarly get 1/3 of the CPUs, and the
executors will get 1/3 as well in total.
See the following link for sharing behavior in the root cgroup:
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Resource_Management_Guide/process_behavior.html
was:
We currently have the following layout when there is no system cgroup present
on a machine:
/cgroup: (system processes, including the mesos-slave) 1024 shares
/cgroup/mesos: (no processes) 1024 shares
/cgroup/mesos/executor1: X shares
...
/cgroup/mesos/executorN: X shares
This does not ensure the slave gets a fair share of the cpu, especially when
there is load inside the root cgroup. This is because the slave is contending
with other processes inside the root cgroup. If the administrators set up a
system cgroup, the layout looks as follows:
/cgroup: (no processes)
/cgroup/system: (system processes, including the mesos-slave) 1024 shares
/cgroup/mesos: (no processes) 1024 shares
/cgroup/mesos/executor1: X shares
...
/cgroup/mesos/executorN: X shares
This still does not ensure the slave gets a fair share for the same reasons.
However, if we create a cgroup to hold only the slave:
/cgroup: (no processes)
/cgroup/system: (system processes) 1024 shares
/cgroup/mesos-slave: (mesos-slave process) 1024 shares
/cgroup/mesos: (no processes) 1024 shares
/cgroup/mesos/executor1: X shares
...
/cgroup/mesos/executorN: X shares
With the above configuration, the slave will get 1 cpu, system processes will
get 1 cpu, and the executors will get the rest.
See the following link for sharing behavior in the root cgroup:
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Resource_Management_Guide/process_behavior.html
> Current cgroups layout does not ensure the slave gets a fair share of the CPU
> resources.
> ----------------------------------------------------------------------------------------
>
> Key: MESOS-458
> URL: https://issues.apache.org/jira/browse/MESOS-458
> Project: Mesos
> Issue Type: Improvement
> Reporter: Benjamin Mahler
>
> We currently have the following layout when there is no system cgroup present
> on a machine:
> /cgroup: (system processes, including the mesos-slave) 1024 shares
> /cgroup/mesos: (no processes) 1024 shares
> /cgroup/mesos/executor1: X shares
> ...
> /cgroup/mesos/executorN: X shares
> This does not ensure the slave gets a fair share of the cpu, especially when
> there is load inside the root cgroup. This is because the slave is contending
> with other processes inside the root cgroup. If the administrators set up a
> system cgroup, the layout looks as follows:
> /cgroup: (no processes)
> /cgroup/system: (system processes, including the mesos-slave) 1024 shares
> /cgroup/mesos: (no processes) 1024 shares
> /cgroup/mesos/executor1: X shares
> ...
> /cgroup/mesos/executorN: X shares
> This still does not ensure the slave gets a fair share for the same reasons.
> However, if we create a cgroup to hold only the slave:
> /cgroup: (no processes)
> /cgroup/system: (system processes) 1024 shares
> /cgroup/mesos-slave: (mesos-slave process) 1024 shares
> /cgroup/mesos: (no processes) 1024 shares
> /cgroup/mesos/executor1: X shares
> ...
> /cgroup/mesos/executorN: X shares
> With the above configuration, the slave will get 1024 / (1024 + 1024 + 1024)
> = 1/3 of the CPUs, system processes will similarly get 1/3 of the CPUs, and
> the executors will get 1/3 as well in total.
> See the following link for sharing behavior in the root cgroup:
> https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Resource_Management_Guide/process_behavior.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
