Apache components and versions available for Azure HDInsight
In this article, you learn about the Apache Hadoop environment components and versions in Azure HDInsight and the Enterprise Security Package. You also learn how to check the Hadoop component versions in HDInsight.
Apache components available with different HDInsight versions
Azure HDInsight supports multiple Hadoop cluster versions that can be deployed at any time. On April 4, 2017, the default cluster version used by Azure HDInsight was 3.6.
The component versions associated with HDInsight cluster versions are listed in the following table.
The default version for the HDInsight service might change without notice. If you have a version dependency, specify the HDInsight version when you create your clusters with the .NET SDK with Azure PowerShell and the Azure classic CLI.
|Component||HDInsight 4.0||HDInsight 3.6 (default)|
|Apache Hadoop and YARN||3.1.1||2.7.3|
|Apache Hive||3.1.0||1.2.1 (2.1.0 on ESP Interactive Query)|
|Apache Tez Hive2||-||0.8.4|
HDInsight 4.0: Spark 2.4 and Kafka 2.1 are fully supported. However, Spark 2.3 and Kafka 1.1 cluster types are not serviced. HDInsight 3.6: Spark 2.3 and Kafka 1.1 are fully supported.
Check for current Apache component version information
The Hadoop environment component versions associated with HDInsight cluster versions can change with updates to HDInsight. To check the Hadoop components and to verify which versions are being used for a cluster, use the Ambari REST API. The GetComponentInformation command retrieves information about service components. For more information, see the Apache Ambari documentation.
For additional release notes on the latest versions of HDInsight, see HDInsight release notes.
Supported HDInsight versions
Support expiration and retirement for HDInsight versions
Support expiration means that Microsoft no longer provides support for the specific HDInsight version. And it's no longer available through the Azure portal for cluster creation. These versions can still be created by using the Azure CLI or the various SDKs.
Retirement means that existing clusters of an HDInsight version continue to run as is. New clusters of this version can't be created through any means, which includes the CLI and SDKs. Other control plane features, such as manual scaling and autoscaling, also might not work after version retirement. Support isn't available for retired versions.
The following tables list the versions of HDInsight. The support expiration and retirement dates are also provided when they're known.
This table lists the versions of HDInsight that are available in the Azure portal and via other deployment methods like PowerShell and the .NET SDK.
|HDInsight version||VM OS||Release date||Support expiration date||Retirement date||High availability||Availability in the Azure portal|
|HDInsight 4.0||Ubuntu 16.0.4 LTS||September 24, 2018||Yes||Yes|
|HDInsight 3.6||Ubuntu 16.0.4 LTS||April 4, 2017||*June 30, 2021||June 30, 2021||Yes||Yes|
*We are extending the support timeframe for certain HDInsight 3.6 cluster types
|Cluster Type||Framework version||Current support expiration||New support expiration date|
|HDInsight 3.6 Hadoop||2.7.3||Dec 31, 2020||June 30, 2021|
|HDInsight 3.6 Spark||2.3||Dec 31, 2020||June 30, 2021|
|HDInsight 3.6 Spark||2.2||Retired on June 30, 2020|
|HDInsight 3.6 Spark||2.1||Retired on June 30, 2020|
|HDInsight 3.6 Kafka||1.1||Dec 31, 2020||June 30, 2021|
|HDInsight 3.6 Kafka||1.0||Retired on June 30, 2020.|
|HDInsight 3.6 HBase||1.1||Dec 31, 2020||June 30, 2021|
|HDInsight 3.6 Interactive Query||2.1||Dec 31, 2020||June 30, 2021|
|HDInsight 3.6 Storm||1.1||Dec 31, 2020||June 30, 2021|
|HDInsight 3.6 ML Services||9.3||Dec 31, 2020||Dec 31, 2020|
After support for a cluster version expires, it might not be available through the Azure portal. In some cases, cluster versions continue to be available by using the Version parameter in the Windows PowerShell New-AzHDInsightCluster command and the .NET SDK until the version retirement date.
This table lists the versions of HDInsight that aren't available in the Azure portal.
|HDInsight version||HDP version||VM OS||Release date||Support expiration date||Retirement date||High availability||Availability in the Azure portal|
|HDInsight 3.5||HDP 2.5||Ubuntu 16.0.4 LTS||September 30, 2016||September 5, 2017||June 28, 2018||Yes||No|
|HDInsight 3.4||HDP 2.4||Ubuntu 14.0.4 LTS||March 29, 2016||December 29, 2016||January 9, 2018||Yes||No|
|HDInsight 3.3||HDP 2.3||Windows Server 2012 R2||December 2, 2015||June 27, 2016||July 31, 2018||Yes||No|
|HDInsight 3.3||HDP 2.3||Ubuntu 14.0.4 LTS||December 2, 2015||June 27, 2016||July 31, 2017||Yes||No|
|HDInsight 3.2||HDP 2.2||Ubuntu 12.04 LTS or Windows Server 2012 R2||February 18, 2015||March 1, 2016||April 1, 2017||Yes||No|
|HDInsight 3.1||HDP 2.1||Windows Server 2012 R2||June 24, 2014||May 18, 2015||June 30, 2016||Yes||No|
|HDInsight 3.0||HDP 2.0||Windows Server 2012 R2||February 11, 2014||September 17, 2014||June 30, 2015||Yes||No|
|HDInsight 2.1||HDP 1.3||Windows Server 2012 R2||October 28, 2013||May 12, 2014||May 31, 2015||Yes||No|
|HDInsight 1.6||HDP 1.1||October 28, 2013||April 26, 2014||May 31, 2015||No||No|
Highly available clusters with two head nodes are deployed by default for HDInsight version 2.1 and later. They aren't available for HDInsight version 1.6 clusters.
Service-level agreement for HDInsight cluster versions
The service-level agreement is defined as a support window. A support window is the time period that an HDInsight version is supported by Microsoft Customer Service and Support. If the version has passed the support expiration date, the HDInsight cluster is outside the support window. Support expiration for HDInsight version X (after a newer X+1 version is available) is the later of:
- Formula 1: Add 180 days to the date when the HDInsight cluster version X was released.
- Formula 2: Add 90 days to the date when the HDInsight cluster version X+1 is made available in the Azure portal.
The retirement date is the date after which the cluster version can't be created on HDInsight. As of July 31, 2017, you can't resize an HDInsight cluster after its retirement date.
Default node configuration and virtual machine sizes for clusters
For more information on which virtual machine SKUs to select for your cluster, see Azure HDInsight cluster configuration details.