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
Copy file name to clipboardExpand all lines: articles/hdinsight/cluster-reliability-issues.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,28 +12,28 @@ ms.date: 03/28/2024
12
12
13
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
14
15
-
###Issue background
15
+
## Issue background
16
16
17
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
18
19
-
###Required action
19
+
## Required action
20
20
21
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
22
23
23
> [!IMPORTANT]
24
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
25
26
-
####FAQ
26
+
### FAQ
27
27
28
-
#####What happens if there's a VM outage in HDInsight clusters that use these affected HDInsight images?
28
+
#### What happens if there's a VM outage in HDInsight clusters that use these affected HDInsight images?
29
29
30
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
31
32
-
#####Is this issue rectified in the latest HDInsight images?
32
+
#### Is this issue rectified in the latest HDInsight images?
33
33
34
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
35
36
-
#####How do I determine the date of the HDInsight image that my clusters are built on?
36
+
#### How do I determine the date of the HDInsight image that my clusters are built on?
37
37
38
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).
0 commit comments