Skip to content

Commit 4eb8721

Browse files
Merge pull request #262386 from v-akarnase/patch-26
Update hbase-troubleshoot-storage-exception-reset.md
2 parents edd8fe2 + b7f3637 commit 4eb8721

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/hdinsight/hbase/hbase-troubleshoot-storage-exception-reset.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Storage exception after connection reset in Azure HDInsight
33
description: Storage exception after connection reset in Azure HDInsight
44
ms.service: hdinsight
55
ms.topic: troubleshooting
6-
ms.date: 12/31/2022
6+
ms.date: 01/04/2024
77
---
88

99
# Scenario: Storage exception after connection reset in Azure HDInsight
@@ -18,11 +18,11 @@ Unable to create new Apache HBase table.
1818

1919
During a table truncation process, there was a storage connection issue. The table entry was deleted in HBase metadata table. All but one blob file was deleted.
2020

21-
Although there was no folder blob called `/hbase/data/default/ThatTable` sitting in the storage. The WASB driver found the existence of the above the blob file and would not allow to create any blob called `/hbase/data/default/ThatTable` because it assumed the parent folders existed, thus creating table will fail.
21+
Although there was no folder blob called `/hbase/data/default/ThatTable` sitting in the storage. The WASB driver found the existence of the above the blob file and would not allow it to create any blob called `/hbase/data/default/ThatTable` because it assumed the parent folders existed, thus creating table fails.
2222

2323
## Resolution
2424

25-
1. From Apache Ambari UI, restart the active HMaster. This will let one of the two standby HMaster becoming the active one and the new active HMaster will reload the metadata table info. Thus you will not see the `already-deleted` table in HMaster UI.
25+
1. From Apache Ambari UI, restart the active HMaster. This lets one of the two standby HMaster becoming the active one and the new active HMaster will reload the metadata table info. Thus you don't see the `already-deleted` table in HMaster UI.
2626

2727
1. You can find the orphan blob file from UI tools like Cloud Explorer or running command like `hdfs dfs -ls /xxxxxx/yyyyy`. Run `hdfs dfs -rmr /xxxxx/yyyy` to delete that blob. For example, `hdfs dfs -rmr /hbase/data/default/ThatTable/ThatFile`.
2828

0 commit comments

Comments
 (0)