Skip to content

Commit bb6bbc0

Browse files
committed
adding TOC entry
1 parent b3a633f commit bb6bbc0

File tree

2 files changed

+3
-1
lines changed

2 files changed

+3
-1
lines changed

articles/hdinsight/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -49,6 +49,8 @@
4949
href: ./hdinsight-selecting-vm-size.md
5050
- name: Cluster capacity planning
5151
href: ./hdinsight-capacity-planning.md
52+
- name: Cluster management best practices
53+
href: ./hdinsight-cluster-management-best-practices.md
5254
- name: Availability and reliability
5355
href: ./hdinsight-high-availability-linux.md
5456
- name: Compare storage options

articles/hdinsight/hdinsight-cluster-management-best-practices.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ Learn best practices for managing HDInsight clusters.
4242
|---|---|
4343
| No quota | There are quotas for the number of quotas that you can create on your subscription in each region. For more information, see [Capacity planning: quotas](./hdinsight-capacity-planning.md). |
4444
| No more IP addresses available | Each VNet has a limited number of IP addresses. When you create a HDInsight cluster, each node (including zookeeper and gateway nodes) uses some of these allotted IP addresses. When all of the IP addresses are in use, you will encounter this error. |
45-
| Network security group (NSG) rules don't allow HDInsight Resource Provider | If you use NSGs or user-defined routes (UDRs) to control inbound traffic to your HDInsight cluster, you must ensure that your cluster can communicate with critical Azure health and management services. For more information, see [HDInsight management IP addresses](./hdinsight-management-ip-addresses.md) |
45+
| Network security group (NSG) rules don't allow communication with HDInsight resource providers | If you use NSGs or user-defined routes (UDRs) to control inbound traffic to your HDInsight cluster, you must ensure that your cluster can communicate with critical Azure health and management services. For more information, see [Network security group (NSG) service tags for Azure HDInsight](./hdinsight-service-tags.md) |
4646
| Reuse of cluster name | When you use a cluster name that you have used before, you need to wait X number of minutes before recreating the cluster. Otherwise you will see a message that the resource already exists. |
4747

4848
## How do I manage running HDInsight clusters?

0 commit comments

Comments
 (0)