Merge pull request #262395 from v-akarnase/patch-35

Update hbase-troubleshoot-pegged-cpu-region-server.md

Author: prmerger-automator[bot]

articles/hdinsight/hbase/hbase-troubleshoot-pegged-cpu-region-server.md

@@ -3,7 +3,7 @@ title: Pegged CPU in Apache HBase cluster - Azure HDInsight
 description: Troubleshoot pegged CPU on region server in Apache HBase cluster in Azure HDInsight
 ms.service: hdinsight
 ms.topic: troubleshooting
-ms.date: 12/26/2022
+ms.date: 01/04/2024
 ---
 
 # Scenario: Pegged CPU on region server in Apache HBase cluster in Azure HDInsight
@@ -16,11 +16,11 @@ Apache HBase region server process starts occupying close to 200% CPU, causing a
 
 ## Cause
 
-If you are running HBase cluster v3.4, you might have been hit by a potential bug caused by upgrade of jdk to version 1.7.0_151. The symptom we see is region server process starts occupying close to 200% CPU. To verify this, run the `top` command; if there is a process occupying close to 200% CPU get its pid and confirm it is region server process by running `ps -aux | grep`.
+If you are running HBase cluster v3.4, you might have been hit by a potential bug caused by upgrade of jdk to version 1.7.0_151. The symptom we see is region server process starts occupying close to 200% CPU. To verify this, run the `top` command; if there is a process occupying close to 200% CPU get its `pid` and confirm it is region server process by running `ps -aux | grep`.
 
 ## Resolution
 
-1. Install jdk 1.8 on ALL nodes of the cluster as below:
+1. Install jdk 1.8 on ALL nodes of the cluster as given:
 
     * Run the script action `https://raw.githubusercontent.com/Azure/hbase-utils/master/scripts/upgradetojdk18allnodes.sh`. Be sure to select the option to run on all nodes.
 
@@ -34,7 +34,7 @@ If you are running HBase cluster v3.4, you might have been hit by a potential bu
 
 1. From Ambari UI again, restart all HBase services that need restart.
 
-1. Depending on the data on cluster, it might take a few minutes to up to an hour for the cluster to reach stable state. The way you confirm the cluster reaches stable state is by either checking HMaster UI (all region servers should be active) from Ambari (refresh) or from headnode run HBase shell and then run status command.
+1. Depending on the data on cluster, it might take a few minutes to up to an hour for the cluster to reach stable state. To confirm that the cluster has reached a stable state, you can check the HMaster UI (ensure all region servers are active) in Ambari by refreshing the page. Alternatively, you can run the HBase shell from the headnode and then execute the status command.
 
 To verify that your upgrade was successful, check that the relevant HBase processes are started using the appropriate Java version - for instance for region server check as: