Skip to content

Commit 488d4e9

Browse files
Update load-balancer-migration-guidelines.md
1 parent 316496f commit 488d4e9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/hdinsight/load-balancer-migration-guidelines.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -136,7 +136,7 @@ NAT gateway provides outbound network connectivity for the cluster. NSG controls
136136
> [!IMPORTANT]
137137
> * If you experience job slowness or network issues after cluster recreation with a standard load balancer, check the "Total SNAT Connection Count" and "Dropped Packets" on your NAT Gateway. High values may indicate SNAT port exhaustion. To address this, consider implementing one of the following methods:
138138
> * Bind additional IP addresses or IP prefixes to your NAT Gateway. For more information, see [Troubleshoot Azure NAT Gateway connectivity](/azure/nat-gateway/troubleshoot-nat-connectivity) and [Metrics and alerts for Azure NAT Gateway](/azure/nat-gateway/nat-metrics#total-snat-connection-count).
139-
> * Enable private link to the your storage accounts which could reduce SNAT port dependency. For more information, see [Use private endpoints for Azure Storage](/azure/storage/common/storage-private-endpoints).
139+
> * Enable private link to storage accounts which could reduce SNAT port dependency. For more information, see [Use private endpoints for Azure Storage](/azure/storage/common/storage-private-endpoints).
140140
141141
> [!NOTE]
142142
> If you are using an ESP cluster with MFA disabled, ensure to check the MFA status once cluster is recreated using a NAT gateway.

0 commit comments

Comments
 (0)