Skip to content

Commit b794251

Browse files
authored
Update cluster-reliability-issues.md
1 parent d65f9f4 commit b794251

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/hdinsight/cluster-reliability-issues.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -12,28 +12,28 @@ ms.date: 03/28/2024
1212

1313
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.
1414

15-
### Issue background
15+
## Issue background
1616

1717
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.
1818

19-
### Required action
19+
## Required action
2020

2121
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.
2222

2323
> [!IMPORTANT]
2424
> 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.
2525
26-
#### FAQ
26+
### FAQ
2727

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?
2929

3030
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.
3131

32-
##### Is this issue rectified in the latest HDInsight images?
32+
#### Is this issue rectified in the latest HDInsight images?
3333

3434
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.
3535

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?
3737

3838
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).
3939

0 commit comments

Comments
 (0)