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/hdinsight-hadoop-create-linux-clusters-with-secure-transfer-storage.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.date: 03/23/2024
9
9
10
10
# Apache Hadoop clusters with secure transfer storage accounts in Azure HDInsight
11
11
12
-
The [Secure transfer required](../storage/common/storage-require-secure-transfer.md) feature enhances the security of your Azure Storage account by enforcing all requests to your account through a secure connection. This feature and the wasbs scheme are only supported by HDInsight cluster version 3.6 or newer.
12
+
The [Secure transfer required](../storage/common/storage-require-secure-transfer.md) feature enhances the security of your Azure Storage account by enforcing all requests to your account through a secure connection. This feature and the wasbs scheme supported by HDInsight cluster version 3.6 or newer.
13
13
14
14
> [!IMPORTANT]
15
15
> Enabling secure storage transfer after creating a cluster can result in errors using your storage account and is not recommended. It is better to create a new cluster using a storage account with secure transfer already enabled.
@@ -34,10 +34,10 @@ For the Azure CLI command [az storage account create](/cli/azure/storage/account
34
34
35
35
To update an existing storage account with Azure CLI, see [Require secure transfer with Azure CLI](../storage/common/storage-require-secure-transfer.md#require-secure-transfer-with-azure-cli).
36
36
37
-
### Secure transfer error(s)
37
+
### Secure transfer errors
38
38
39
39
40
-
If you accidentally enabled the 'Require secure transfer' option after creating the HDInsight cluster, you may be seeing error messages like the following:
40
+
If you accidentally enabled the 'Require secure transfer' option after creating the HDInsight cluster, you may be seeing error messages as follow:
41
41
42
42
`com.microsoft.azure.storage.StorageException: The account being accessed does not support http.`
43
43
@@ -46,16 +46,16 @@ For Hbase clusters only, you can try the following steps to restore the cluster
46
46
2. Stop HDFS from Ambari.
47
47
3. In Ambari, navigate to HDFS --> Configs --> Advanced --> fs.defaultFS
48
48
4. Change wasb to wasbs and save it.
49
-
5. If you are using the Accelerated Writes feature, the 'hbase.rootDir' under the hbase configs also needs to be changed from wasb to wasbs.
49
+
5. If you're using the Accelerated Writes feature, the 'hbase.rootDir' under the hbase configs also needs to be changed from wasb to wasbs.
50
50
6. Restart all required services.
51
51
52
-
## Add additional storage accounts
52
+
## Add more storage accounts
53
53
54
-
There are several options to add additional secure transfer enabled storage accounts:
54
+
There are several options to add more secure transfer enabled storage accounts:
55
55
56
56
* Modify the Azure Resource Manager template in the last section.
57
57
* Create a cluster using the [Azure portal](https://portal.azure.com) and specify linked storage account.
58
-
* Use script action to add additional secure transfer enabled storage accounts to an existing HDInsight cluster. For more information, see [Add additional storage accounts to HDInsight](hdinsight-hadoop-add-storage.md).
58
+
* Use script action to add more secure transfer enabled storage accounts to an existing HDInsight cluster. For more information, see [Add more storage accounts to HDInsight](hdinsight-hadoop-add-storage.md).
0 commit comments