This is the documentation for Cloudera Manager 5.0.x. Documentation for other versions is available at Cloudera Documentation.

Linux Control Groups

Cloudera Manager supports the Linux control groups (cgroups) kernel feature. With cgroups, administrators can impose per-resource restrictions and limits on services and roles. This provides the ability to allocate resources using cgroups to enable isolation of compute frameworks from one another. Resource allocation is implemented by setting properties for the services and roles.

Linux Distribution Support

Cgroups are a feature of the Linux kernel, and as such, support depends on the host's Linux distribution and version. As shown in the following table, Linux cgroups don't exist on RHEL 5. However, all of the other OS platforms supported by Cloudera Manager support cgroups.

Distribution	CPU Shares	I/O Weight	Memory Soft Limit	Memory Hard Limit
Red Hat Enterprise Linux (or CentOS) 5
Red Hat Enterprise Linux (or CentOS) 6
SUSE Linux Enterprise Server 11
Ubuntu 10.04 LTS
Ubuntu 12.04 LTS
Debian 6.0
Debian 7.0

If a distribution lacks support for a given parameter, changes to the parameter have no effect.

The exact level of support can be found in the Cloudera Manager Agent log file, shortly after the Agent has started. See Viewing Cloudera Manager Server and Agent Logs to find the Agent log. In the log file, look for an entry like this:

Found cgroups capabilities: {'has_memory': True, 'default_memory_limit_in_bytes': 9223372036854775807,
'writable_cgroup_dot_procs': True, 'has_cpu': True,
'default_blkio_weight': 1000, 'default_cpu_shares': 1024, 'has_blkio': True}

The has_memory and similar entries correspond directly to support for the CPU, I/O, and memory parameters.

Resource Management with Control Groups

In order to use cgroups, you must also enable cgroup-based resource management under the Host > Resource Management configuration properties. However, if you configure static service pools, this property will be set as part of that process.

Enabling Resource Management

Cgroups-based resource management can be enabled for all hosts, or on a per-host basis.

If you've upgraded from a version of Cloudera Manager older than Cloudera Manager 4.5, restart every Cloudera Manager Agent before using cgroups-based resource management:
1. Stop all services, including the Cloudera Management Service.
2. On each cluster host, run as root:
```
$ service cloudera-scm-agent hard_restart
```
3. Start all services.
Click the Hosts tab.
Optionally click the link for the host where you want to enable cgroups.
Select Configuration > View and Edit.
Select the Resource Management category.
Check Enable Cgroup-based Resource Management checkbox.
Restart all roles on the host or hosts.

Limitations

Role group and role instance override cgroup-based resource management parameters must be saved one at a time. Otherwise some of the changes that should be reflected dynamically will be ignored.
The role group abstraction is an imperfect fit for resource management parameters, where the goal is often to take a numeric value for a host resource and distribute it amongst running roles. The role group represents a "horizontal" slice: the same role across a set of hosts. However, the cluster is often viewed in terms of "vertical" slices, each being a combination of slave roles (such as TaskTracker, DataNode, Region Server, Impala daemon, and so on). Nothing in Cloudera Manager guarantees that these disparate horizontal slices are "aligned" (meaning, that the role assignment is identical across hosts). If they are unaligned, some of the role group values will be incorrect on unaligned hosts. For example a host whose role groups have been configured with memory limits but that's missing a role will probably have unassigned memory.

Configuring Resource Parameters

After enabling cgroups, you can restrict and limit the resource consumption of roles (or role groups) on a per-resource basis. All of these parameters can be found in the Cloudera Manager Admin Console, under the Resource Management category:

CPU Shares - The more CPU shares given to a role, the larger its share of the CPU when under contention. Until processes on the host (including both roles managed by Cloudera Manager and other system processes) are contending for all of the CPUs, this will have no effect. When there is contention, those processes with higher CPU shares will be given more CPU time. The effect is linear: a process with 4 CPU shares will be given roughly twice as much CPU time as a process with 2 CPU shares.
Updates to this parameter will be dynamically reflected in the running role.
I/O Weight - The greater the I/O weight, the higher priority will be given to I/O requests made by the role when I/O is under contention (either by roles managed by Cloudera Manager or by other system processes). This only affects read requests; write requests remain unprioritized.
Updates to this parameter will be dynamically reflected in the running role.
Memory Soft Limit - When the limit is reached, the kernel will reclaim pages charged to the process if and only if the host is facing memory pressure. If reclaiming fails, the kernel may kill the process. Both anonymous as well as page cache pages contribute to the limit.
After updating this parameter, the role must be restarted before changes take effect.
Memory Hard Limit - When a role's resident set size (RSS) exceeds the value of this parameter, the kernel will swap out some of the role's memory. If it's unable to do so, it will kill the process. Note that the kernel measures memory consumption in a manner that doesn't necessarily match what the top or ps report for RSS, so expect that this limit is a rough approximation.
After updating this parameter, the role must be restarted before changes take effect.

Example: Protecting Production MapReduce Jobs from Impala Queries

Suppose you have MapReduce deployed in production and want to roll out Impala without affecting production MapReduce jobs. For simplicity, we will make the following assumptions:

The cluster is using homogenous hardware
Each worker host has two cores
Each worker host has 8 GB of RAM
Each worker host is running a DataNode, TaskTracker, and an Impala daemon
Each role type is in a single role group
Cgroups-based resource management has been enabled on all hosts

Action	Procedure
CPU	Leave DataNode and TaskTracker role group CPU shares at 1024. Set Impala daemon role group's CPU shares to 256. The TaskTracker role group should be configured with a Maximum Number of Simultaneous Map Tasks of 2 and a Maximum Number of Simultaneous Reduce Tasks of 1. This yields an upper bound of three MapReduce tasks at any given time; this is an important detail for memory sizing.
Memory	Set Impala daemon role group memory limit to 1024 MB. Leave DataNode maximum Java heap size at 1 GB. Leave TaskTracker maximum Java heap size at 1 GB. Leave MapReduce Child Java Maximum Heap Size for Gateway at 1 GB. Leave cgroups hard memory limits alone. We'll rely on "cooperative" memory limits exclusively, as they yield a nicer user experience than the cgroups-based hard memory limits.
I/O	Leave DataNode and TaskTracker role group I/O weight at 500. Impala daemon role group I/O weight is set to 125.

When you're done with configuration, restart all services for these changes to take effect.

The results are:

When MapReduce jobs are running, all Impala queries together will consume up to a fifth of the cluster's CPU resources.
Individual Impala daemons won't consume more than 1 GB of RAM. If this figure is exceeded, new queries will be cancelled.
DataNodes and TaskTrackers can consume up to 1 GB of RAM each.
We expect up to 3 MapReduce tasks at a given time, each with a maximum heap size of 1 GB of RAM. That's up to 3 GB for MR tasks.
The remainder of each host's available RAM (6 GB) is reserved for other host processes.
When MapReduce jobs are running, read requests issued by Impala queries will receive a fifth of the priority of either HDFS read requests or MapReduce read requests.

Page generated September 3, 2015.