You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: Cluster reliability issue with older images in HDInsight clusters
3
+
description: Cluster reliability issue with older images in HDInsight clusters
4
+
ms.service: hdinsight
5
+
ms.topic: troubleshooting-known-issue
6
+
ms.date: 03/28/2024
7
+
---
8
+
9
+
# Cluster reliability issue with older images in HDInsight clusters
10
+
11
+
**Issue published date**: October 13, 2023
12
+
13
+
As part of the proactive reliability management of Azure HDInsight, we recently found a potential reliability issue on HDInsight clusters that use images dated February 2022 or older.
14
+
15
+
## Issue background
16
+
17
+
In HDInsight images dated before March 2022, a known bug was discovered on one particular Azure Linux build. The Microsoft Azure Linux Agent (`waagent`), a lightweight process that manages virtual machines, was unstable and resulted in VM outages. HDInsight clusters that consumed the Azure Linux build have experienced service outages, job failures, and adverse effects on features like IPsec and autoscale.
18
+
19
+
## Required action
20
+
21
+
If your cluster was created before March 2022, we advise rebuilding your cluster with the latest HDInsight image. Support for cluster images dated before March 2022 ended on November 10, 2023. These images won't receive security updates, bug fixes, or patches, leaving them highly susceptible to vulnerabilities.
22
+
23
+
> [!IMPORTANT]
24
+
> We recommend that you keep your clusters updated to the latest HDInsight version on a regular basis. Using clusters that are based on the latest HDInsight image ensures that they have the latest operating system patches, security patches, bug fixes, and library versions. This practice helps you minimize risk and potential security vulnerabilities.
25
+
26
+
### FAQ
27
+
28
+
#### What happens if there's a VM outage in HDInsight clusters that use these affected HDInsight images?
29
+
30
+
You can't recover such virtual machines through straightforward restarts. The outage could last for several hours and require manual intervention from the Microsoft support team.
31
+
32
+
#### Is this issue rectified in the latest HDInsight images?
33
+
34
+
Yes. We fixed this issue on HDInsight images dated on or after March 1, 2022. We advise that you move to the latest stable version to maintain the service-level agreement (SLA) and service reliability.
35
+
36
+
#### How do I determine the date of the HDInsight image that my clusters are built on?
37
+
38
+
The last 10 digits in your HDInsight image version indicate the date and time of the image. For example, an image version of 5.0.3000.1.2208310943 indicates a date of August 31, 2022. [Learn how to verify your HDInsight image version](/azure/hdinsight/view-hindsight-cluster-image-version).
39
+
40
+
41
+
#### Resources
42
+
43
+
-[Create HDInsight clusters by using automation](/azure/hdinsight/hdinsight-hadoop-provision-linux-clusters#cluster-setup-methods)
**Support expiration** means that Microsoft no longer provides support for the specific HDInsight version. You might not be able to create clusters from the Azure portal.
Copy file name to clipboardExpand all lines: articles/hdinsight/hdinsight-known-issues.md
+6-59Lines changed: 6 additions & 59 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Azure HDInsight known issues
3
3
description: Track known issues for Azure HDInsight, along with troubleshooting steps, actions, and frequently asked questions.
4
4
ms.service: hdinsight
5
5
ms.topic: troubleshooting-known-issue
6
-
ms.date: 10/13/2023
6
+
ms.date: 03/28/2024
7
7
---
8
8
9
9
# Azure HDInsight known issues
@@ -14,75 +14,22 @@ For service-level outages or degradation notifications, check the [Azure Service
14
14
15
15
## Summary of known issues
16
16
17
-
Azure HDInsight has the following known issues:
17
+
Azure HDInsight Open known issues:
18
18
19
19
| HDInsight component | Issue description |
20
20
|---------------------|-------------------|
21
-
| Kafka |[Kafka 2.4.1 validation error in ARM templates](#kafka-241-validation-error-in-arm-templates)|
22
-
| Platform |[Cluster reliability issue with older images in HDInsight clusters](#cluster-reliability-issue-with-older-images-in-hdinsight-clusters)|
21
+
| Kafka |[Kafka 2.4.1 validation error in ARM templates](./kafka241-validation-error-arm-templates.md)|
22
+
| Platform |[Cluster reliability issue with older images in HDInsight clusters](./cluster-reliability-issues.md)|
23
23
24
-
### Kafka 2.4.1 validation error in ARM templates
25
24
26
-
**Issue published date**: October 13, 2023
27
-
28
-
When you're submitting cluster creation requests by using Azure Resource Manager templates (ARM templates), runbooks, PowerShell, the Azure CLI, and other automation tools, you might receive a "BadRequest" error message if you specify `clusterType = "Kafka"`, `HDI version = "5.0"`, and `Kafka version = "2.4.1"`.
29
-
30
-
#### Troubleshooting steps
31
-
32
-
When you're using [templates or automation tools](/azure/hdinsight/hdinsight-hadoop-provision-linux-clusters#cluster-setup-methods) to create HDInsight Kafka clusters, choose `componentVersion = "2.4"`. This value enables you to successfully create a Kafka 2.4.1 cluster in HDInsight 5.0.
33
-
34
-
#### Resources
35
-
36
-
-[Create HDInsight clusters by using automation](/azure/hdinsight/hdinsight-hadoop-provision-linux-clusters#cluster-setup-methods)
### Cluster reliability issue with older images in HDInsight clusters
42
-
43
-
**Issue published date**: October 13, 2023
44
-
45
-
As part of the proactive reliability management of Azure HDInsight, we recently found a potential reliability issue on HDInsight clusters that use images dated February 2022 or older.
46
-
47
-
#### Issue background
48
-
49
-
In HDInsight images dated before March 2022, a known bug was discovered on one particular Azure Linux build. The Microsoft Azure Linux Agent (`waagent`), a lightweight process that manages virtual machines, was unstable and resulted in VM outages. HDInsight clusters that consumed the Azure Linux build have experienced service outages, job failures, and adverse effects on features like IPsec and autoscale.
50
-
51
-
#### Required action
52
-
53
-
If your cluster was created before March 2022, we advise rebuilding your cluster with the latest HDInsight image. Support for cluster images dated before March 2022 ended on November 10, 2023. These images won't receive security updates, bug fixes, or patches, leaving them highly susceptible to vulnerabilities.
54
-
55
-
> [!IMPORTANT]
56
-
> We recommend that you keep your clusters updated to the latest HDInsight version on a regular basis. Using clusters that are based on the latest HDInsight image ensures that they have the latest operating system patches, security patches, bug fixes, and library versions. This practice helps you minimize risk and potential security vulnerabilities.
57
-
58
-
#### FAQ
59
-
60
-
##### What happens if there's a VM outage in HDInsight clusters that use these affected HDInsight images?
61
-
62
-
You can't recover such virtual machines through straightforward restarts. The outage could last for several hours and require manual intervention from the Microsoft support team.
63
-
64
-
##### Is this issue rectified in the latest HDInsight images?
65
-
66
-
Yes. We fixed this issue on HDInsight images dated on or after March 1, 2022. We advise that you move to the latest stable version to maintain the service-level agreement (SLA) and service reliability.
67
-
68
-
##### How do I determine the date of the HDInsight image that my clusters are built on?
69
-
70
-
The last 10 digits in your HDInsight image version indicate the date and time of the image. For example, an image version of 5.0.3000.1.2208310943 indicates a date of August 31, 2022. [Learn how to verify your HDInsight image version](/azure/hdinsight/view-hindsight-cluster-image-version).
71
-
72
-
#### Resources
73
-
74
-
-[Create HDInsight clusters by using automation](/azure/hdinsight/hdinsight-hadoop-provision-linux-clusters#cluster-setup-methods)
|Not applicable|Spark|Conda Version Regression in a recent HDInsight release|October 13, 2023|Closed|
32
+
|Not applicable|Spark|[Conda Version Regression in a recent HDInsight release](./hdinsight-known-issues-conda-version-regression.md)|October 13, 2023|Closed|
title: Kafka 2.4.1 validation error in Azure Resource Manager templates
3
+
description: Kafka 2.4.1 validation error in ARM templates Known Issue
4
+
ms.service: hdinsight
5
+
ms.topic: troubleshooting-known-issue
6
+
ms.date: 03/26/2024
7
+
---
8
+
9
+
# Kafka 2.4.1 validation error in ARM templates
10
+
11
+
**Issue published date**: October 13, 2023
12
+
13
+
When you're submitting cluster creation requests by using Azure Resource Manager templates (ARM templates), runbooks, PowerShell, the Azure CLI, and other automation tools, you might receive a "BadRequest" error message if you specify `clusterType = "Kafka"`, `HDI version = "5.0"`, and `Kafka version = "2.4.1"`.
14
+
15
+
## Troubleshooting steps
16
+
17
+
When you're using [templates or automation tools](/azure/hdinsight/hdinsight-hadoop-provision-linux-clusters#cluster-setup-methods) to create HDInsight Kafka clusters, choose `componentVersion = "2.4"`. This value enables you to successfully create a Kafka 2.4.1 cluster in HDInsight 5.0.
18
+
19
+
## Resources
20
+
21
+
-[Create HDInsight clusters by using automation](/azure/hdinsight/hdinsight-hadoop-provision-linux-clusters#cluster-setup-methods)
0 commit comments