Hardware Requirements Guide

• 5 GB for the Event Database
• 20 GB for the Event Server Index Directory. The location of this directory is set by the Event Server Index Directory Event Server configuration property.

• 100-1000 tablets: 4 GB
• 10,000 or more tablets with 200 or more Tablet Servers: 8 GB
• 10,000 or more tablets with 300 or more Tablet Servers: 12 GB

Set this value using the Tablet Server Max Heapsize Accumulo configuration property.

See Flume Memory Consumption

• Minimum: 512 MB Java Heap
• Recommended: 8 GB
• Medium scale production (200 or more tablets per Tablet Server): 16 GB

Set this value using the Tablet Server Max Heapsize Accumulo configuration property.

• 4 or more spindles for each HDFS DataNode
• 1 disk for local logs (this disk can be shared with the operating system and/or other Hadoop logs

Set this value using the Tracer Max Heapsize Accumulo configuration property.

Set this value using the Garbage Collector Max Heapsize Accumulo configuration property.

Set this value using the Monitor Max Heapsize Accumulo configuration property.

• Minimum: 1 GB
• Maximum 4 GB
• Java Heap size should be greater than the maximum channel capacity

Set this value using the Java Heap Size of Agent in Bytes Flume configuration property.

See Flume Memory Consumption

(Number of sources + Number of sinks ) / 2

Set this value using the Java Heap Size of JournalNode in Bytes HDFS configuration property.

• Minimum: 1 GB (for proof-of-concept deployments)
• Add an additional 1 GB for each additional 1,000,000 blocks

  Snapshots and encryption can increase the required heap memory.

See Sizing NameNode Heap Memory

Set this value using the Java Heap Size of NameNode in Bytes HDFS configuration property.

• Minimum of 2 dedicated disks for metadata
• 1 dedicated disk for log files (This disk may be shared with the operating system.)
• Maximum disks: 4

Minimum: 4 GB

Increase the memory for higher replica counts or a higher number of blocks per DataNode. When increasing the memory, Cloudera recommends an additional 1 GB of memory for every 1 million replicas above 4 million on the DataNodes. For example, 5 million replicas require 5 GB of memory.

Set this value using the Java Heap Size of DataNode in Bytes HDFS configuration property.

Minimum: 4

Maximum: 24

The maximum acceptable size will vary depending upon how large average block size is. The DN’s scalability limits are mostly a function of the number of replicas per DN, not the overall number of bytes stored. That said, having ultra-dense DNs will affect recovery times in the event of machine or rack failure. Cloudera does not support exceeding 100 TB per data node. You could use 12 x 8 TB spindles or 24 x 4TB spindles. Cloudera does not support drives larger than 8 TB.

• 100-10,000 regions: 4 GB
• 10,000 or more regions with 200 or more Region Servers: 8 GB
• 10,000 or more regions with 300 or more Region Servers: 12 GB

Set this value using the Java Heap Size of HBase Master in Bytes HBase configuration property.

• Minimum: 8 GB
• Medium-scale production: 16 GB
• Heap larger than 16 GB requires special Garbage Collection tuning. See Configuring the HBase BlockCache

Set this value using the Java Heap Size of HBase RegionServer in Bytes HBase configuration property.

Set this value using the Java Heap Size of HBase Thrift Server in Bytes HBase configuration property.

Minimum 1 disk

This disk is required for the following:

• HiveServer2 log files
• stdout and stderr output files
• Configuration files
• Operation logs stored in the operation_logs_dir directory, which is configurable
• Any temporary files that might be created by local map tasks under the /tmp directory

Cloudera recommends splitting HiveServer2 into multiple instances and load balancing them once you start allocating more than 12 GB to HiveServer2. The objective is to adjust the size to reduce the impact of Java garbage collection on active processing by the service.

Set this value using the Java Heap Size of HiveServer2 in Bytes Hive configuration property.

For more information, see Tuning Hive in CDH.

Minimum 1 disk

This disk is required so that the Hive metastore can store the following artifacts:

• Logs
• Configuration files
• Backend database that is used to store metadata if the database server is also hosted on the same node

Set this value using the Java Heap Size of Hive Metastore Server in Bytes Hive configuration property.

For more information, see Tuning Hive in CDH.

• Minimum: 4 GB
• Maximum 10 GB
• If the cluster uses the Hue load balancer, add additional memory

When Hue is configured for high availability, add additional cores

When Hue is configured for high availability, add temp space is required

• Minimum: 32 GB
• Recommended: 128 GB

• Minimum: 4 GB
• Recommended: 8 GB

• Minimum: 4
• Recommended: 16 or more

CPU instruction set: AVX2

• Minimum: 1 disk
• Recommended: 8 or more

• Minimum: 4 GB
• Recommended: 8 GB

In Cloudera Manager, use the Java Heap Size of Catalog Server in Bytes configuration property (Cloudera Manager 5.7 and higher), or Impala Catalog Server Environment Advanced Configuration Snippet (Safety Valve) (Cloudera Manager 5.6 and lower).

If not using Cloudera Manager, use the JAVA_TOOL_OPTIONS environment variable. For example, to set it to 8 GB: JAVA_TOOL_OPTIONS= "-Xmx8g"

• Minimum: 4
• Recommended: 16 or more

CPU instruction set: AVX2

• Minimum and Recommended: 1 disk

• RAM: 64 GB
• Recommended Java heap: 4 GB

Set this value using the Java Heap Size of Broker Kafka configuration property.

See

• 1 HDD For operating system
• 1 HDD for Zookeeper dataLogDir
• 10- HDDs, using Raid 10, for Kafka data

Set this value using the Java Heap Size of MirrorMaker Kafka configuration property.

• Minimum: 4 GB
• Recommended: 10 GB

Additional hardware may be required, depending on the workloads running in the cluster. If you are using Impala, see the Impala sizing guidelines.

• Minimum: 256 MB
• Recommended: 1 GB

• Minimum: 1 GB (this is the default set by Cloudera Manager). This is sufficient for less than 10 simultaneous workflows, without forking.
• If you notice excessive garbage collection, or out-of-memory errors, increase the heap size to 4 GB for medium-size production clusters or to 8 GB for large-size production clusters.
• Set this value using the Java Heap Size of Oozie Server in Bytes Oozie configuration property.

• Small workloads, or evaluations: 16 GB
• Smaller production environments: 32 GB
• Larger production environments: 96 GB is sufficient for most clusters.

Set this value using the Java Heap Size of Solr Server in Bytes Solr configuration property.

See

• Minimum: 4
• Recommended: 16 for production workloads

• Minimum: 576 MB
• Recommended: 2.5 GB per million objects in the Hive database (servers, databases, tables, partitions, columns, URIs, and views)

Set this value with the Java Heap Size of Sentry Server in Bytes Sentry configuration property.

Set this value using the Java Heap Size of History Server in Bytes Spark configuration property.

1

• Minimum: 1 GB
• Increase memory by 1.6 GB for each 100,000 tasks kept in memory. For example:

  5 jobs @ 100, 000 mappers + 20,000 reducers = 600,000 total tasks requiring 9.6 GB of heap.

  See the Other Recommendations column for additional tuning suggestions.

Set this value using the Java Heap Size of JobHistory Server in Bytes YARN configuration property.

• Set the mapreduce.jobhistory.jhist.format property to binary (history files will load about 2x-3x faster with this setting). Available in CDH 5.5.0 or higher only.

• Set the mapreduce.jobhistory.loadedtasks.cache.size property to a total loaded task count. Using the example in the Java Heap column to the left, of 650,000 total tasks, you can set it to 700,000 to allow for some safety margin. This should also prevent the JobHistoryServer from hanging during garbage collection, since the job count limit does not have a task limit.

• It is strongly recommended to enable G1GC if the heap is large (larger than 10 GB).
• It is strongly recommended to set mapreduce.jobhistory.loadedjob.tasks.max so that jobs that have too many tasks will not be loaded and cached in memory. Such jobs can be retrieved by using the command line: mapred job -history <jobId>

Configure additional heap memory for the following conditions:

• Large number of containers
• Large shuffle sizes in Spark or MapReduce

Set this value using the Java Heap Size of NodeManager in Bytes YARN configuration property.

• Minimum: 8-16 cores
• Recommended: 32-64 cores

Set this value using the Java Heap Size of ResourceManager in Bytes YARN configuration property.

• Set the ApplicationMaster Memory YARN configuration property to 512 MB
• Set the Container Memory Minimum YARN configuration property to 1 GB.

• Minimum: 1 GB
• Increase heap size when watching 10,000 - 100,000 ephemeral znodes and are using 1,000 or more clients.

Set this value using the Java Heap Size of ZooKeeper Server in Bytes ZooKeeper configuration property.

ZooKeeper was not designed to be a low-latency service and does not benefit from the use of SSD drives. The ZooKeeper access patterns – append-only writes and sequential reads – were designed with spinning disks in mind. Therefore Cloudera recommends using HDD drives.