Skip to content

Commit 6633826

Browse files
authored
Improved Acrolinx Score
Improved Acrolinx Score
1 parent 96f946d commit 6633826

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/hdinsight/hdinsight-hadoop-create-linux-clusters-with-secure-transfer-storage.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.date: 03/23/2024
99

1010
# Apache Hadoop clusters with secure transfer storage accounts in Azure HDInsight
1111

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

1414
> [!IMPORTANT]
1515
> 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
3434

3535
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).
3636

37-
### Secure transfer error(s)
37+
### Secure transfer errors
3838

3939

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:
4141

4242
`com.microsoft.azure.storage.StorageException: The account being accessed does not support http.`
4343

@@ -46,16 +46,16 @@ For Hbase clusters only, you can try the following steps to restore the cluster
4646
2. Stop HDFS from Ambari.
4747
3. In Ambari, navigate to HDFS --> Configs --> Advanced --> fs.defaultFS
4848
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.
5050
6. Restart all required services.
5151

52-
## Add additional storage accounts
52+
## Add more storage accounts
5353

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:
5555

5656
* Modify the Azure Resource Manager template in the last section.
5757
* 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).
5959

6060
## Next steps
6161

0 commit comments

Comments
 (0)