To configure memory allocations, determine how many entities are being monitored and
then consult the tables below for required and recommended memory configurations.
To determine the number of entities being monitored:
-
Go to .
- Locate the chart with the title Cloudera Management Service Monitored
Entities.
The number of monitored entities for the Host Monitor
and Service Monitor displays at the bottom of the chart. In the following example, the
Host Monitor has 46 monitored entities and the Service Monitor has 230 monitored
entities.
- Use the number of monitored entities for the Host Monitor to determine its memory
requirements and recommendations in the tables below.
- Use the number of monitored entities for the Service Monitor to determine its
memory requirements and recommendations in the tables below.
Clusters with
HDFS, YARN, or ImpalaUse the recommendations in this table for clusters where the
only services having worker roles are HDFS, YARN, or Impala.
| Number of Monitored Entities |
Number of Hosts |
Required Java Heap Size |
Recommended Non-Java Heap Size |
| 0-2,000 |
0-100 |
1 GB |
6 GB |
| 2,000-4,000 |
100-200 |
1.5 GB |
6 GB |
| 4,000-8,000 |
200-400 |
1.5 GB |
12 GB |
| 8,000-16,000 |
400-800 |
2.5 GB |
12 GB |
| 16,000-20,000 |
800-1,000 |
3.5 GB |
12 GB |
Clusters with HBase, Solr, Kafka, or KuduUse the
recommendations when services such as HBase, Solr, Kafka, or Kudu are deployed in the
cluster. These services typically have larger quantities of monitored
entities.
| Number of Monitored Entities |
Number of Hosts |
Required Java Heap Size |
Recommended Non-Java Heap Size |
| 0-30,000 |
0-100 |
2 GB |
12 GB |
| 30,000-60,000 |
100-200 |
3 GB |
12 GB |
| 60,000-120,000 |
200-400 |
3.5 GB |
12 GB |
| 120,000-240,000 |
400-800 |
8 GB |
20 GB |
