-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #2 from yanancai/master
Release 2020-10-08
- Loading branch information
Showing
1 changed file
with
40 additions
and
10 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,31 +1,61 @@ | ||
# Release date: 10/08/2020 | ||
|
||
This release applies for both HDInsight 3.6 and HDInsight 4.0. HDInsight release is made available to all regions over several days. The release date here indicates the first region release date. If you don't see below changes, wait for the release being live in your region in several days. | ||
|
||
## New features | ||
### HDInsight private clusters with no public IP and Private link (Preview) | ||
HDInsight now supports creating clusters with no public IP and private link access to the clusters in preview. Customers can use the new advanced networking settings to create a fully isolated cluster with no public IP and use their own private endpoints to access the cluster. | ||
|
||
### Moving to Azure virtual machine scale sets | ||
HDInsight now uses Azure virtual machines to provision the cluster. Starting from this release, the service will gradually migrate to [Azure virtual machine scale sets](https://docs.microsoft.com/azure/virtual-machine-scale-sets/overview). The entire process may take months. After your regions and subscriptions are migrated, newly created HDInsight clusters will run on virtual machine scale sets without customer actions. No breaking change is expected. | ||
|
||
## Deprecation | ||
### Deprecation of HDInsight 3.6 ML Services cluster | ||
HDInsight 3.6 ML Services cluster type will be end of support by Dec 31 2020. Customers won't create new 3.6 ML Services clusters after that. Existing clusters will run as is without the support from Microsoft. Check the support expiration for HDInsight versions and cluster types [here](https://docs.microsoft.com/azure/hdinsight/hdinsight-component-versioning#available-versions). | ||
|
||
## Behavior changes | ||
No behavior change for this release. | ||
|
||
## Upcoming changes | ||
The following changes will happen in upcoming releases. | ||
|
||
### Ability to select different Zookeeper virtual machine sizes for Spark, Hadoop, and ML Services | ||
HDInsight today doesn't support customizing Zookeeper node size for Spark, Hadoop, and ML Services cluster types. It defaults to A2_v2/A2 virtual machine sizes, which are provided free of charge. In the upcoming release, you can select a Zookeeper virtual machine size that is most appropriate for your scenario. Zookeeper nodes with virtual machine size other than A2_v2/A2 will be charged. A2_v2 and A2 virtual machines are still provided free of charge. | ||
|
||
## Bug fixes | ||
HDInsight continues to make cluster reliability and performance improvements. | ||
|
||
## Component version change | ||
No component version change for this release. You can find the current component versions for HDInsight 4.0 and HDInsight 3.6 in [this doc](https://docs.microsoft.com/azure/hdinsight/hdinsight-component-versioning#apache-hadoop-components-available-with-different-hdinsight-versions). | ||
|
||
# Release date: 09/28/2020 | ||
|
||
This release applies for both HDInsight 3.6 and HDInsight 4.0. HDInsight release is made available to all regions over several days. The release date here indicates the first region release date. If you don't see below changes, wait for the release being live in your region in several days. | ||
|
||
# New features | ||
## Autoscale for Interactive Query with HDInsight 4.0 is now generally available | ||
## New features | ||
### Autoscale for Interactive Query with HDInsight 4.0 is now generally available | ||
Auto scale for Interactive Query cluster type is now General Available (GA) for HDInsight 4.0. All Interactive Query 4.0 clusters created after 27 August 2020 will have GA support for auto scale. | ||
|
||
## HBase cluster supports Premium ADLS Gen2 | ||
### HBase cluster supports Premium ADLS Gen2 | ||
HDInsight now supports Premium ADLS Gen2 as primary storage account for HDInsight HBase 3.6 and 4.0 clusters. Together with [Accelerated Writes](https://docs.microsoft.com/azure/hdinsight/hbase/apache-hbase-accelerated-writes), you can get better performance for your HBase clusters. | ||
|
||
## Kafka partition distribution on Azure fault domains | ||
### Kafka partition distribution on Azure fault domains | ||
A fault domain is a logical grouping of underlying hardware in an Azure data center. Each fault domain shares a common power source and network switch. Before HDInsight Kafka may store all partition replicas in the same fault domain. Starting from this release, HDInsight now supports automatically distribution of Kafka partitions based on Azure fault domains. | ||
|
||
## Encryption in transit | ||
### Encryption in transit | ||
Customers can enable encryption in transit between cluster nodes using IPSec encryption with platform-managed keys. This option can be enabled at the cluster creation time. See more details about [how to enable encryption in transit](https://docs.microsoft.com/azure/hdinsight/domain-joined/encryption-in-transit). | ||
|
||
## Encryption at host | ||
### Encryption at host | ||
When you enable encryption at host, data stored on the VM host is encrypted at rest and flows encrypted to the storage service. From this release, you can **Enable encryption at host on temp data disk** when creating the cluster. Encryption at host is only supported on [certain VM SKUs in limited regions](https://docs.microsoft.com/azure/virtual-machines/linux/disks-enable-host-based-encryption-portal). HDInsight supports the [following node configuration and SKUs](https://docs.microsoft.com/azure/hdinsight/hdinsight-supported-node-configuration). See more details about [how to enable encryption at host](https://docs.microsoft.com/azure/hdinsight/disk-encryption#encryption-at-host-using-platform-managed-keys). | ||
|
||
## Moving to Azure virtual machine scale sets | ||
### Moving to Azure virtual machine scale sets | ||
HDInsight now uses Azure virtual machines to provision the cluster. Starting from this release, the service will gradually migrate to [Azure virtual machine scale sets](https://docs.microsoft.com/azure/virtual-machine-scale-sets/overview). The entire process may take months. After your regions and subscriptions are migrated, newly created HDInsight clusters will run on virtual machine scale sets without customer actions. No breaking change is expected. | ||
|
||
# Upcoming changes | ||
## Upcoming changes | ||
The following changes will happen in upcoming releases. | ||
|
||
## Ability to select different Zookeeper SKU for Spark, Hadoop, and ML Services | ||
### Ability to select different Zookeeper SKU for Spark, Hadoop, and ML Services | ||
HDInsight today doesn't support changing Zookeeper SKU for Spark, Hadoop, and ML Services cluster types. It uses A2_v2/A2 SKU for Zookeeper nodes and customers aren't charged for them. In the upcoming release, customers can change Zookeeper SKU for Spark, Hadoop, and ML Services as needed. Zookeeper nodes with SKU other than A2_v2/A2 will be charged. The default SKU will still be A2_V2/A2 and free of charge. | ||
|
||
# Component version change | ||
## Component version change | ||
No component version change for this release. You can find the current component versions for HDInsight 4.0 and HDInsight 3.6 in [this doc](https://docs.microsoft.com/azure/hdinsight/hdinsight-component-versioning#apache-hadoop-components-available-with-different-hdinsight-versions). |