What are the default and recommended node configurations for Azure HDInsight?
Artikkel
This article discusses default and recommended node configurations for Azure HDInsight clusters.
Default and minimum recommended node configuration and virtual machine sizes for clusters
The following tables list default and recommended virtual machine (VM) sizes for HDInsight clusters. This information is necessary to understand the VM sizes to use when you're creating PowerShell or Azure CLI scripts to deploy HDInsight clusters.
If you need more than 32 worker nodes in a cluster, select a head node size with at least 8 cores and 14 GB of RAM.
The only cluster types that have data disks are Kafka and HBase clusters with the Accelerated Writes feature enabled. HDInsight supports P30 and S30 disk sizes in these scenarios. For all other cluster types, HDInsight provides managed disk space with the cluster. From 11/07/2019 onwards, the managed disk size of each node in the newly created cluster is 128 GB. This can't be changed.
The specifications of all minimum recommended VM types used in this document are summarized in the following table.
To get the SKU identifier for use in powershell and other scripts, add Standard_ to the beginning of all of the VM SKUs in the tables below. For example, D12_v2 would become Standard_D12_v2.
Cluster type
Hadoop
HBase
Interactive Query
Spark
Kafka
Head: default VM size
E4_v3
E4_v3
D13_v2
E8_v3, D13_v2*
E4_v3
Head: minimum recommended VM sizes
D5_v2
D3_v2
D13_v2
D12_v2, D13_v2*
D3_v2
Worker: default VM size
E8_v3
E4_v3
D14_v2
E8_v3
4 E4_v3 with 2 S30 disks per broker
Worker: minimum recommended VM sizes
D5_v2
D3_v2
D13_v2
D12_v2
D3_v2
ZooKeeper: default VM size
A4_v2
A4_v2
A4_v2
ZooKeeper: minimum recommended VM sizes
A4_v2
A4_v2
A4_v2
* = VM Sizes for Spark Enterprise Security Package (ESP) clusters
Obs!
Worker is known as Region for the HBase cluster type.