Enabling YARN CGroups to Limit the Container CPU Usage
Scenario
CGroups is a Linux kernel feature. It groups task sets and their subsets into hierarchical structures with customizable behavior. In YARN, CGroups limits the resources (such as CPU usage) allocated to containers. This feature significantly simplifies the process of limiting container CPU usage.
Currently, CGroups is only used for limiting the CPU usage.
Configuration Description
For details about how to configure CPU isolation and secure CGroups, visit the Hadoop official website:
Versions earlier than MRS 3.2.0: https://hadoop.apache.org/docs/r3.1.1/hadoop-yarn/hadoop-yarn-site/NodeManagerCgroups.html
MRS 3.2.0 or later: https://hadoop.apache.org/docs/r3.3.1/hadoop-yarn/hadoop-yarn-site/NodeManagerCgroups.html
CGroups is a Linux kernel feature and is enabled using LinuxContainerExecutor. For details about how to configure the LinuxContainerExecutor for security, see the official website. You can learn the file system permissions assigned to users and user groups from the official documentation at:
Versions earlier than MRS 3.2.0: https://hadoop.apache.org/docs/r3.1.1/hadoop-project-dist/hadoop-common/SecureMode.html#LinuxContainerExecutor
MRS 3.2.0 or later: https://hadoop.apache.org/docs/r3.3.1/hadoop-project-dist/hadoop-common/SecureMode.html#LinuxContainerExecutor
- Do not modify users, user groups, and related permissions of various paths in the corresponding file system. Otherwise, functions of CGroups may become abnormal.
- If the parameter value of yarn.nodemanager.resource.percentage-physical-cpu-limit is too small, the number of available cores may be less than one. For example, if the parameter of a four-core node is set to 20%, the number available core is less than one. As a result, all cores will be used. Certain Linux distributions, such as CentOS, do not support the quota mode. In this scenario, you can use the cpuset mode.
The table below describes the parameter for configuring cpuset mode, that is, only configured CPUs can be used by YARN.
| Parameter | Description | Default Value |
|---|---|---|
| yarn.nodemanager.linux-container-executor.cgroups.cpu-set-usage | Whether to enable the cpuset mode. If this parameter is set to true, the cpuset mode is enabled. | false |
The table below describes the parameters for configuring the strictcpuset mode, that is, only configured CPUs can be used by containers.
| Parameter | Description | Default Value |
|---|---|---|
| yarn.nodemanager.linux-container-executor.cgroups.cpu-set-usage | Whether to enable the cpuset mode. If this parameter is set to true, the cpuset mode is enabled. | false |
| yarn.nodemanager.linux-container-executor.cgroups.cpuset.strict.enabled | Whether containers use allocated CPUs. If this parameter is set to true, the container can use the allocated CPUs. | false |
To switch from cpuset mode to quota mode, the following conditions must be met:
- Set the yarn.nodemanager.linux-container-executor.cgroups.cpu-set-usage parameter to false.
- Delete the container folder (if any) from the /sys/fs/cgroup/cpuset/hadoop-yarn/ directory.
- Delete all CPUs configured in the cpuset.cpus file in /sys/fs/cgroup/cpuset/hadoop-yarn/.
Procedure
- Log in to Manager. Choose Cluster > Name of the desired cluster > Services > Yarn > Configurations and select All Configurations.
- In the navigation pane on the left, choose NodeManager > Customization and find the yarn-site.xml file.
- Add the parameters in Table 1 and Table 2 as user-defined parameters.

Based on the configuration files and parameter functions, locate the row where parameter yarn-site.xml resides. Enter the parameter name in the Name column and enter the parameter value in the Value column.
Click + to add a customized parameter.
- Click Save. In the displayed Save Configuration dialog box, confirm the modification and click OK. Click Finish when the system displays "Operation succeeded". The configuration is successfully saved.
After saving the configuration, restart the YARN services whose configuration has expired for the changes to take effect.
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot