Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 8612294

Browse files
committedMar 15, 2022
Fix typo
java -> Java
1 parent 2d80cfb commit 8612294

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed
 

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ If you are running HBase cluster v3.4, you might have been hit by a potential bu
3636

3737
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.
3838

39-
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:
39+
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:
4040

4141
```
4242
ps -aux | grep regionserver, and verify the version like '''/usr/lib/jvm/java-8-openjdk-amd64/bin/java

0 commit comments

Comments
 (0)
Please sign in to comment.