发行说明Release notes

本文提供有关最新 Azure HDInsight 版本更新的信息。This article provides information about the most recent Azure HDInsight release updates. 有关较早版本的信息,请参阅 HDInsight 发行说明存档For information on earlier releases, see HDInsight Release Notes Archive.

摘要Summary

Azure HDInsight 是 Azure 中最受企业客户青睐的开源分析服务之一。Azure HDInsight is one of the most popular services among enterprise customers for open-source analytics on Azure.

发行日期:01/09/2020Release date: 01/09/2020

此发行版适用于 HDInsight 3.6 和 4.0。This release applies both for HDInsight 3.6 and 4.0.

重要

Linux 是 HDInsight 3.4 或更高版本上使用的唯一操作系统。Linux is the only operating system used on HDInsight version 3.4 or greater. 有关详细信息,请参阅 HDInsight 版本控制文章For more information, see HDInsight versioning article.

新增功能New features

强制执行 TLS 1.2TLS 1.2 enforcement

传输层安全性 (TLS) 和安全套接字层 (SSL) 是提供计算机网络通信安全的加密协议。Transport Layer Security (TLS) and Secure Sockets Layer (SSL) are cryptographic protocols that provide communications security over a computer network. 详细了解 TLSLearn more about TLS. HDInsight 在公共 HTTPs 终结点上使用 TLS 1.2,但仍支持使用 TLS 1.1 以实现后向兼容。HDInsight uses TLS 1.2 on public HTTPs endpoints but TLS 1.1 is still supported for backward compatibility.

在此发行版中,客户只能为通过公共群集终结点建立的所有连接启用 TLS 1.2。With this release, customers can opt into TLS 1.2 only for all connections through the public cluster endpoint. 为了支持此方案,我们引入了新属性 minSupportedTlsVersion,在创建群集期间可以指定此属性。To support this, the new property minSupportedTlsVersion is introduced and can be specified during cluster creation. 如果不设置该属性,群集仍支持 TLS 1.0、1.1 和 1.2,这与当前的行为相同。If the property is not set, the cluster still supports TLS 1.0, 1.1 and 1.2, which is the same as today's behavior. 客户可将此属性的值设置为“1.2”,这意味着,群集仅支持 TLS 1.2 和更高版本。Customers can set the value for this property to "1.2", which means that the cluster only supports TLS 1.2 and above. 有关详细信息,请参阅规划虚拟网络 - 传输层安全性For more information, see Plan a virtual network - Transport Layer Security.

创建自己的密钥进行磁盘加密Bring your own key for disk encryption

通过 Azure 存储服务加密 (SSE) 保护 HDInsight 中的所有托管磁盘。All managed disks in HDInsight are protected with Azure Storage Service Encryption (SSE). 这些磁盘上的数据默认已使用 Microsoft 托管的密钥进行加密。Data on those disks is encrypted by Microsoft-managed keys by default. 从此发行版开始,可以创建自己的密钥 (BYOK) 进行磁盘加密,并使用 Azure Key Vault 管理该密钥。Starting from this release, you can Bring Your Own Key (BYOK) for disk encryption and manage it using Azure Key Vault. BYOK 加密是创建群集期间完成的单步配置,不额外收费。BYOK encryption is a one-step configuration during cluster creation with no additional cost. 只需将 HDInsight 作为托管标识注册到 Azure Key Vault,并在创建群集时添加加密密钥。Just register HDInsight as a managed identity with Azure Key Vault and add the encryption key when you create your cluster. 有关详细信息,请参阅客户管理的密钥磁盘加密For more information, see Customer-managed key disk encryption.

弃用Deprecation

此版本无弃用。No deprecations for this release. 若要为即将到来的弃用做好准备,请参阅即将推出的变更To get ready for upcoming deprecations, see Upcoming changes.

行为更改Behavior changes

此版本无行为变更。No behavior changes for this release. 若要为即将推出的更改做好准备,请参阅即将推出的更改To get ready for upcoming changes, see Upcoming changes.

即将推出的更改Upcoming changes

即将发布的版本中将推出以下变更。The following changes will happen in upcoming releases.

提供至少有 4 个核心的 VM 作为头节点A minimum 4-core VM is required for Head Node

提供至少有 4 个核心的 VM 作为头节点是为了确保 HDInsight 群集的高可用性和可靠性。A minimum 4-core VM is required for Head Node to ensure the high availability and reliability of HDInsight�clusters. 从 2020 年 4 月 6 日开始,客户只能选择至少有 4 个核心的 VM 作为新 HDInsight 群集的头节点。Starting from April 6th 2020, customers can only choose 4-core or above VM as Head Node for the new HDInsight clusters. 现有群集将继续按预期方式运行。Existing clusters will continue to run as expected.

迁移到 Azure 虚拟机规模集Moving to Azure virtual machine scale sets

HDInsight 目前使用 Azure 虚拟机来预配群集。HDInsight now uses Azure virtual machines to provision the cluster. 在即将推出的发行版中,HDInsight 将改用 Azure 虚拟机规模集。In the upcoming release, HDInsight will use Azure virtual machine scale sets instead. 详细了解 Azure 虚拟机规模集。See more about Azure virtual machine scale sets.

HBase 2.0 到 2.1HBase 2.0 to 2.1

在即将推出的 HDInsight 4.0 版本中,HBase 版本将从 2.0 升级到 2.1。In the upcoming HDInsight 4.0 release, HBase version will be upgraded from version 2.0 to 2.1.

Bug 修复Bug fixes

HDInsight 会持续改善群集的可靠性和性能。HDInsight continues to make cluster reliability and performance improvements.

组件版本更改Component version change

此发行版未发生组件版本更改。No component version change for this release. 可在此处查找 HDInsight 4.0 和 HDInsight 3.6 的当前组件版本。You could find the current component versions for HDInsight 4.0 ad HDInsight 3.6 here.

已知问题Known issues

从 2020 年 1 月 29 日起,在尝试使用 Jupyter 笔记本时,可能会收到错误。As of January 29, 2020, there is an active issue in which you may receive an error when attempting to use a Jupyter notebook. 请执行以下步骤来解决该问题。Use the steps below to fix the issue. 还可以参阅此 MSDN 文章StackOverflow 文章了解最新信息,或提出其他问题。You can also refer to this MSDN post or this StackOverflow post for up-to-date information, or to ask additional questions. 解决问题后,此页将会更新。This page will be updated when the issue is fixed.

错误Errors

  • 值错误:无法将笔记本转换为 v5,因为该版本不存在ValueError: Cannot convert notebook to v5 because that version doesn't exist
  • 加载笔记本时出错 加载此笔记本时出现未知错误。Error loading notebook An unknown error occurred while loading this notebook. 此版本可以加载格式为 v4 或更早版本的笔记本This version can load notebook formats v4 or earlier

原因Cause

群集上的 _version.py 文件已更新为 5.x.x,而不是 4.4.x.## 或需要重启 Ambari。The _version.py file on the cluster was updated to 5.x.x instead of 4.4.x.## or Ambari needs to be restarted.

解决方案Solution

如果在创建新的 Jupyter 笔记本时遇到上面列出的某个错误,请执行以下步骤来解决问题。If you create a new Jupyter notebook and receive one of the errors listed above, perform the following steps to fix the issue.

  1. 转到 https://CLUSTERNAME.azurehdinsight.cn(其中 CLUSTERNAME 是群集的名称),在 Web 浏览器中打开 Ambari。Open Ambari in a web browser by going to https://CLUSTERNAME.azurehdinsight.cn, where CLUSTERNAME is the name of your cluster.

  2. 在 Ambari 的左侧菜单中单击“Jupyter”,然后在“服务操作”中单击“停止”。 In Ambari, on the left menu, click Jupyter, then on Service Actions, click Stop.

  3. 通过 SSH 连接到运行 Jupyter 服务的群集头节点。ssh into the cluster headnode where the Jupyter service is running.

  4. 在 sudo 模式下打开 /usr/bin/anaconda/lib/python2.7/site-packages/nbformat/_version.py 文件。Open the following file /usr/bin/anaconda/lib/python2.7/site-packages/nbformat/_version.py in sudo mode.

  5. 检查 version_info 的值。Check the value of version_info.

  6. 如果 version_info 的值设置为:If the value of version_info is set to:

    version_info = (5, 0, 3)version_info = (5, 0, 3)

    请将该条目修改为以下内容:Then modify the entry to:

    version_info = (4, 4, 0)version_info = (4, 4, 0)

    保存文件。And save the file.

    如果 version_info 已设置为 (4, 4, 0),则继续执行下一步,因为只需要重启 Ambari,不需要进行其他更改。If version_info is already set to (4, 4, 0), then continue to the next step as only Ambari needs to be restarted, no additional changes are needed.

  7. 返回到 Ambari,在“服务操作”中单击“全部重启”。 Go back to Ambari, and in Service Actions, click Restart All.