CDH 5.4 on VMware with Isilon as DFS
This document is a high-level design and best-practices guide for deploying Cloudera Enterprise on a VMware vSphere®-based infrastructure with a shared storage back end.
This document describes the architecture for running Cloudera Enterprise on VMware vSphere-based infrastructure with shared Isilon-based storage.
NOTE: This is a work in progress and details will change as software versions and capabilities change.
Audience and Scope
This guide is for IT architects who are responsible for the design and deployment of virtualized infrastructure and a shared storage platform in the data center, as well as for Hadoop administrators and architects who will be data center architects or engineers or who collaborate with specialists in that space.
This document describes Cloudera recommendations on the following topics:
- Storage Area Network considerations
- Storage array considerations
- Data network considerations
- Virtualization hardware/platform considerations
- Virtualization strategy for the Cloudera software stack
Glossary of Terms
|DataNode||Worker nodes of the cluster to which the HDFS data is written.|
|DRS||Distributed Resource Scheduler. The software that controls movement of VMs and storage on a VMware cluster.|
|HBA||Host bus adapter. An I/O controller that is used to interface a host with storage devices.|
|HDD||Hard disk drive.|
|HDFS||Hadoop Distributed File System.|
Configuration that addresses availability issues in a cluster. In a standard configuration, the NameNode is a single point of failure (SPOF). Each cluster has a single NameNode, and if that machine or process became unavailable, the cluster as a whole is unavailable until the NameNode is either restarted or brought up on a new host. The secondary NameNode does not provide failover capability.
High availability enables running two NameNodes in the same cluster: the active NameNode and the standby NameNode. The standby NameNode allows a fast failover to a new NameNode in case of machine crash or planned maintenance.
|HVE||Hadoop Virtualization Extensions. Enables proper placement of data blocks and scheduling of YARN jobs in a virtualized environment in which multiple copies of any single block of data or YARN jobs are not placed/scheduled on VMs that reside on the same hypervisor host. The YARN component of HVE is work in progress and won’t be supported in CDH 5.4 (YARN-18).|
|JBOD||Just a bunch of disks. In contrast to disks configured through software or hardware with redundancy mechanisms for data protection.|
|Job History Server||Process that archives job metrics and metadata. One per cluster.|
|LBT||Load-based teaming. A teaming policy that is traffic-load aware and ensures physical NIC capacity of a NIC team is optimized.|
|LRO||This stands for Large Receive Offload and is a technique used to improve throughput of network connections. It is done by coalescing multiple incoming packets from a single stream into a large receive buffer before passing them up the networking stack.|
|LUN||Logical unit number. Logical units allocated from a storage array to a host. This looks like a SCSI disk to the host, but it is only a logical volume on the storage array side.|
|NameNode||The metadata master of HDFS essential for the integrity and proper functioning of the distributed filesystem.|
|NIC||Network interface card.|
|NIOC||Network I/O Control.|
|NodeManager||The process that starts application processes and manages resources on the DataNodes.|
|NUMA||Non-uniform memory access. Addresses memory access latency in multi-socket servers, where memory that is remote to a core (that is, local to another socket) needs to be accessed. This is typical of SMP (symmetric multiprocessing) systems, and there are several strategies to optimize applications and operating systems. vSphere ESXi can be optimized for NUMA. It can also present the NUMA architecture to the virtualized guest OS, which can then leverage it to optimize memory access. This is called vNUMA.|
|PDU||Power distribution unit.|
Quorum Journal Manager. Provides a fencing mechanism for high availability in a Hadoop cluster. This service is used to distribute HDFS edit logs to multiple hosts (at least three are required) from the active NameNode. The standby NameNode reads the edits from the JournalNodes and constantly applies them to its own namespace. In case of a failover, the standby NameNode applies all of the edits from the JournalNodes before promoting itself to the active state.
Quorum JournalNodes. Nodes on which the journal services are installed.
|RDM||Raw device mappings. Used to configure storage devices (usually logical unit numbers (LUNs)) directly to virtual machines running on VMware.|
|RM||ResourceManager. The resource management component of YARN. This initiates application startup and controls scheduling on the DataNodes of the cluster (one instance per cluster).|
|SAN||Storage area network.|
|SIOC||Storage I/O Control.|
|ToR||Top of rack.|
|TSO||TCP segmentation offload|
|vMotion||VMware term for live migration of virtual machines across physical hosts.|
|ZK||ZooKeeper. A centralized service for maintaining configuration information, naming, and providing distributed synchronization and group services.|
Isilon Distributed Storage Array for HDFS and VMware-based VMs as Compute Nodes
This model decouples the HDFS DataNode functionality from the YARN NodeManager and other components of Cloudera Enterprise.
In this architecture, Isilon acts as the HDFS/storage layer, and the VMs only provide the compute resources needed.
Considerations for a storage component are not required; however, from a vSphere design perspective, the storage component must be factored into the distributed vSwitch design. This is noted in the vSphere design consideration section.
Physical Cluster Topology
Physical Hypervisor Cluster Component List
|Physical servers||Two-socket, 6-10 cores per socket > 2 GHz; minimally 256 GB RAM.||vSphere hosts that house the various VMs/guests.||TBD (based on cluster design).|
Dual-port 10 Gbps Ethernet NICs.
The connector type depends on the network design; could be SFP+ or Twinax.
|Provide the data network services for the VMware vSphere cluster.||At least two per physical server.|
|Internal HDDs||Standard OS sizes.||The ESXi hypervisor requires little storage, so size is not important. These ensure continuity of service on server resets.||Two per physical server.|
|Ethernet ToR/leaf switches||Minimally 10 Gbps switches with sufficient port density to accommodate the VMware cluster. These require enough ports to create a realistic spine-leaf topology providing ISL bandwidth above a 1:4 oversubscription ratio (preferably 1:1).||Although most enterprises have mature data network practices, consider building a dedicated data network for the Hadoop cluster.||At least two per rack.|
|Ethernet spine switches||Minimally 10 Gbps switches with sufficient port density to accommodate incoming ISL links and ensure required throughput over the spine (for inter-rack traffic).||Same considerations as for ToR switches.||Depends on the number of racks.|
Logical Cluster Topology
For the YARN NodeManagers, data protection at the HDFS level is not required, because the VMs are running only the compute part of the cluster.
The minimum requirements to build out the cluster are:
- 3 Master Nodes (VMs)
- 5 YARN NodeManagers (VMs)
The following table identifies service roles for different node types.
Create Distributed Resource Scheduler (DRS) rules so that there is strong negative affinity between the master node VMs. This ensures that no two master nodes are provisioned or migrated to the same physical vSphere host. Alternately, you can do this when provisioning through vSphere Big Data Extensions by specifying "instancePerHost=1", which asserts that any host server should have at most one instance of a MasterNode VM. (See the BDE CLI guide (PDF) for more details.)
|Master Node||Master Node||Master Node||YARN NodeManager nodes 1..n|
|Hive||MetaStore, WebHCat, HiveServer2|
|Management (misc)||Cloudera Agent||Cloudera Agent||Cloudera Agent, Oozie, Cloudera Manager, Management Services||Cloudera Agent|
|Navigator||Navigator, Key Management Services|
NOTE: Low-latency workloads are subject to network latency, because all data traffic between compute nodes and HDFS (Isilon-based) is north-south traffic.
The following table provides size recommendations for the VMs. This depends on the size of the physical hardware provisioned, as well as the amount of HDFS storage and the services running on the cluster.
two-socket with 6-10 cores/socket > 2GHz; minimally 128 GB RAM; 4-6 disks
|These can be VMs or bare-metal. If VMs, do not house the RM node and the standby in the same chassis (or blade chassis if using blades).||These nodes house the Cloudera Master services and serve as the gateway/edge device that connects the rest of the customer’s network to the Cloudera cluster.||Three (for scaling up to 100 cluster nodes).|
two-socket with 6-10 cores/socket > 2GHz; minimally 128 GB RAM
|These are VMs that can be deployed as needed on the vSphere cluster, without oversubscription of either CPU or memory resources.||
These nodes house the YARN node managers as well as additional required services.
Adjust memory sizes based on the number of services, or provision additional capacity to run additional services.
|TDB (based on customer needs).|
The following table provides recommendations for storage allocation.
||Avoid fracturing the filesystem layout into multiple smaller filesystems. Instead, keep a separate “/” and “/var”.|
|YARN NodeManager nodes||
||Avoid fracturing the filesystem layout into multiple smaller filesystems. Instead, keep a separate “/” and “/var”. For example, for 10 TB of total storage in Isilon, 2 TB is needed for intermediate storage. If storage is SAN-based, for 20 nodes, reserve 100 GB LUNs/datastores/VMDKs to each node.|
5.4.4 and higher
|5.4||184.108.40.206||All services except Navigator|
VMware vSphere Design Considerations
Network Switch Configuration
Standard vswitches can be employed, and need to be configured for each ESXi host in the cluster. The key configuration parameter to consider is the MTU size, ensuring that the same MTU size is set at the physical switches, guest OS, ESXi VMNIC, and the vswitch layers. This is relevant when enabling jumbo frames, which is recommended for Hadoop environments.
Disk Multipathing Configuration
Disk multipathing (DMP) policy uses round robin (RR). The storage array vendor might have specific recommendations. Not every vendor supports RR, so use an appropriate DMP algorithm.
This has little impact on this deployment model. Use best practices for provisioning storage for the OS drives and intermediate drives.
Storage Group Configuration
Each provisioned disk is mapped to either:
- One vSphere datastore (which in turn contains one VMDK or virtual disk), or
- One raw device mapping (RDM)
NOTE: In this case, this is only relevant for the OS disks and any intermediate storage disks that might be provisioned in the cluster.
Set up virtual disks in “independent persistent” mode for optimal performance. Eager Zeroed Thick virtual disks provide the best performance.
Partition alignment at the VMFS layer depends on the storage vendor. Misaligned storage impacts performance.
Disable SIOC, and disable storage DRS.
vSphere Tuning Best Practices
Power Policy is an ESXi parameter. The balanced mode may be the best option. In some cases, performance might be more important than power optimization. Evaluate your environment and choose accordingly.
Avoid memory and CPU overcommitment. Use large pages for Hypervisor.
For network tuning, enable advanced features such as TSO, LRO, scatter gather, interrupt coalescing, and so on.
Guest OS Considerations
Special tuning parameters may be needed to optimize performance of the guest OS in a virtualized environment. In general, normal tuning guidelines apply, but specific tuning might be needed depending on the virtualization driver used.
Generic Best Practices
Minimize unnecessary virtual hardware devices. Choose the appropriate virtual hardware version; check the latest version and understand its capabilities.
NIC Driver Type
VMXNET3 is supported in RHEL 6.x and CentOS 6.x with the installation of VMware tools.
- Tune the MTU size for jumbo frames at the guest level as well as ESXi and switch level.
- Enable TCP segmentation offload (TSO) at the ESXi level (should be enabled by default). This can be leveraged only by VMXNET3 drivers at the Guest layer.
- Similarly, other offload features can be leveraged only when using the VMXNET3 driver.
- Use regular platform tuning parameters, such as ring buffer size. However, RSS and RPS tuning must be specific to the VMXNET3 driver.
HBA Driver Type
Use a PVSCSI storage adapter. This provides the best performance characteristics (reduced CPU utilization and increased throughput), and is optimal for I/O-intensive guests (as with Hadoop).
- Tune queue depth in the guest OS SCSI driver.
- Disk partition alignment—If VMFS is already aligned, this is typically not necessary.
The I/O scheduler used for the OS disks might need to be different if using VMDKS. Instead of using CFQ, use deadline or noop elevators. Performance varies and must be tested. Any performance gains must be quantified appropriately (for example, 1-2% improvement vs. 10-20% improvement).
Minimize anonymous paging by setting vm.swappiness=1.
Consider using virtual NUMA (vNUMA). This exposes the NUMA architecture to the guest OS so that the guest OS can be tuned to leverage NUMA during scheduling. Virtual Hardware version 8 or later is required to leverage vNUMA.
Cloudera Software Stack
Guidelines for installing the Cloudera stack on this platform are nearly identical to those for bare-metal. This is addressed in various documents on the Cloudera website.
- Performance Best Practices for VMware vSphere® 5.5 (PDF)
- Exploring the hadoop network topology (blog)
- Virtualized Hadoop Performance with vSphere 5.1
- Hadoop Deployment Guide for vSphere
- vmware BDE Command line Guide
- Cloudera Documentation
- EMC Hadoop Starter Kit -- Step By Step Guide To Quickly And Easily Deploy Hadoop
- EMC HSK 3.0 For Cloudera Enterprise