Skip to content

Commit 44c54c6

Browse files
authored
updated hdionaks files
1 parent 69cee4f commit 44c54c6

File tree

3 files changed

+8
-5
lines changed

3 files changed

+8
-5
lines changed

articles/hdinsight-aks/hdinsight-on-aks-autoscale-clusters.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Automatically scale Azure HDInsight on AKS clusters
33
description: Use the Auto scale feature to automatically scale Azure HDInsight clusters on AKS based on a schedule or load based metrics.
44
ms.service: hdinsight-aks
55
ms.topic: how-to
6-
ms.date: 08/29/2023
6+
ms.date: 02/06/2024
77
---
88

99
# Auto Scale HDInsight on AKS Clusters
@@ -167,7 +167,7 @@ The default value is set to **180 seconds**
167167
> * Your subscription has a capacity quota for each region. The total number of cores of your head nodes and the maximum worker nodes can't exceed the capacity quota. However, this quota is a soft limit; you can always create a support ticket to get it increased easily.
168168
> * If you exceed the total core quota limit, You'll receive an error message saying `The maximum node count you can select is {maxCount} due to the remaining quota in the selected subscription ({remaining} cores)`.
169169
> * Scale Up rules take precedence when one or more rules are triggered. Even if only one of the rules for scale up suggest cluster being under-provisioned, cluster will try to scale up. For scale down to happen, no scale up rule should be triggered.
170-
> * The maximum number of nodes allowed in a cluster pool is 250 in public preview.
170+
> * In public preview, HDInsight on AKS supports upto 500 nodes in a cluster.
171171

172172
### Create a cluster with a Resource Manager template
173173

articles/hdinsight-aks/manual-scale.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Manual scale
33
description: How to manually scale in HDInsight on AKS.
44
ms.service: hdinsight-aks
55
ms.topic: how-to
6-
ms.date: 08/29/2023
6+
ms.date: 02/06/2024
77
---
88

99
# Manual scale
@@ -51,7 +51,7 @@ If you **remove nodes** (scale down) from an HDInsight on AKS cluster:
5151
|Question|Answer|
5252
| -------- | -------- |
5353
|What are the minimum nodes that I can add/remove during scale operations?|One Node.|
54-
|What's the maximum limit to scale up an HDInsight on AKS Trino cluster?|100 nodes (in public preview).|
54+
|How many nodes are supported by HDInsight on AKS cluster?|500 nodes per cluster (in public preview).|
5555
|How do I manually scale down my cluster?|In the ARM request, update `computeProfile.count` or follow the steps mentioned to scale down using Azure portal.|
5656
|Can I add custom script actions to a cluster during manual scale?|Script actions are applicable for Apache Spark cluster type|
5757
|How do I get logs for manual scale failures for the cluster nodes?|Logs are available in Log analytics module, refer the [Azure Monitor Integration](./how-to-azure-monitor-integration.md).|

articles/hdinsight-aks/required-outbound-traffic.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,13 +3,16 @@ title: Outbound traffic on HDInsight on AKS
33
description: Learn required outbound traffic on HDInsight on AKS.
44
ms.service: hdinsight-aks
55
ms.topic: conceptual
6-
ms.date: 08/29/2023
6+
ms.date: 02/06/2024
77
---
88

99
# Required outbound traffic for HDInsight on AKS
1010

1111
[!INCLUDE [feature-in-preview](includes/feature-in-preview.md)]
1212

13+
> [!NOTE]
14+
> HDInsight on AKS uses Azure CNI network model by default. For more information, see [Azure CNI networking](../aks/concepts-network.md#azure-cni-overlay-networking).
15+
1316
This article outlines the networking information to help manage the network policies at enterprise and make necessary changes to the network security groups (NSGs) for smooth functioning of HDInsight on AKS.
1417

1518
If you use firewall to control outbound traffic to your HDInsight on AKS cluster, you must ensure that your cluster can communicate with critical Azure services.

0 commit comments

Comments
 (0)