Skip to content

Commit f465794

Browse files
Merge pull request #114592 from hrasheed-msft/hdiquotarequest
new doc on requesting CPU core quota increases
2 parents cae8428 + 1de0d97 commit f465794

File tree

6 files changed

+75
-36
lines changed

6 files changed

+75
-36
lines changed

articles/hdinsight/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,8 @@
5959
href: ./hdinsight-selecting-vm-size.md
6060
- name: Cluster capacity planning
6161
href: ./hdinsight-capacity-planning.md
62+
- name: Request increase for CPU core quota
63+
href: ./quota-increase-request.md
6264
- name: Cluster management best practices
6365
href: ./cluster-management-best-practices.md
6466
- name: Availability and reliability

articles/hdinsight/hdinsight-capacity-planning.md

Lines changed: 2 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.reviewer: jasonh
77
ms.service: hdinsight
88
ms.topic: conceptual
99
ms.custom: hdinsightactive
10-
ms.date: 04/07/2020
10+
ms.date: 05/07/2020
1111
---
1212

1313
# Capacity planning for HDInsight clusters
@@ -82,48 +82,14 @@ You're charged for a cluster's lifetime. If there are only specific times that y
8282

8383
> [!NOTE]
8484
> When a cluster is deleted, its default Hive metastore is also deleted. To persist the metastore for the next cluster re-creation, use an external metadata store such as Azure Database or [Apache Oozie](https://oozie.apache.org/).
85-
<!-- see [Using external metadata stores](hdinsight-using-external-metadata-stores.md). -->
8685
8786
### Isolate cluster job errors
8887

8988
Sometimes errors can occur because of the parallel execution of multiple maps and reduce components on a multi-node cluster. To help isolate the issue, try distributed testing. Run concurrent multiple jobs on a single worker node cluster. Then expand this approach to run multiple jobs concurrently on clusters containing more than one node. To create a single-node HDInsight cluster in Azure, use the *`Custom(size, settings, apps)`* option and use a value of 1 for *Number of Worker nodes* in the **Cluster size** section when provisioning a new cluster in the portal.
9089

9190
## Quotas
9291

93-
After determining your target cluster VM size, scale, and type, check the current quota capacity limits of your subscription. When you reach a quota limit, you can't deploy new clusters. Or scale out existing clusters by adding more worker nodes. The only quota limit is the CPU Cores quota that exists at the region level for each subscription. For example, your subscription may have 30 core limit in the East US region.
94-
95-
To check your available cores, do the following steps:
96-
97-
1. Sign in to the [Azure portal](https://portal.azure.com/).
98-
2. Navigate to the **Overview** page for the HDInsight cluster.
99-
3. On the left menu, select **Quota limits**.
100-
101-
The page displays the number of cores in use, the number of available cores, and the total cores.
102-
103-
If you need to request a quota increase, do the following steps:
104-
105-
1. Sign in to the [Azure portal](https://portal.azure.com/).
106-
1. Select **Help + support** on the bottom-left side of the page.
107-
1. Select **New support request**.
108-
1. On the **New support request** page, under **Basics** tab, select the following options:
109-
110-
- **Issue type**: **Service and subscription limits (quotas)**
111-
- **Subscription**: the subscription you want to modify
112-
- **Quota type**: **HDInsight**
113-
114-
![Create a support request to increase HDInsight core quota](./media/hdinsight-capacity-planning/hdinsight-quota-support-request.png)
115-
116-
1. Select **Next: Solutions >>**.
117-
1. On the **Details** page, enter a description of the issue, select the severity of the issue, your preferred contact method, and other required fields.
118-
1. Select **Next: Review + create >>**.
119-
1. On the **Review + create** tab, select **Create**.
120-
121-
> [!NOTE]
122-
> If you need to increase the HDInsight core quota in a private region, [submit a whitelist request](https://aka.ms/canaryintwhitelist).
123-
124-
You can [contact support to request a quota increase](https://docs.microsoft.com/azure/azure-portal/supportability/resource-manager-core-quotas-request).
125-
126-
There are some fixed quota limits. For example, a single Azure subscription can have at most 10,000 cores. For details on these limits, see [Azure subscription and service limits, quotas, and constraints](https://docs.microsoft.com/azure/azure-resource-manager/management/azure-subscription-service-limits).
92+
For more information on managing subscription quotas, see [Requesting quota increases](quota-increase-request.md).
12793

12894
## Next steps
12995

81.1 KB
Loading
53.5 KB
Loading
133 KB
Loading
Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
1+
---
2+
title: CPU Core quota increase request - Azure HDInsight
3+
description: Learn the process to request an increase for the CPU cores allocated to your subscription.
4+
author: hrasheed-msft
5+
ms.author: hrasheed
6+
ms.reviewer: jasonh
7+
ms.service: hdinsight
8+
ms.topic: conceptual
9+
ms.custom: hdinsightactive
10+
ms.date: 05/07/2020
11+
---
12+
# Requesting quota increases for Azure HDInsight
13+
14+
CPU core quotas help to ensure that resource usage is distributed fairly between all customers in a particular Azure region. However, in certain cases, your business requirements might demand more cluster resources than your current quota will allow. In such cases, you can request a CPU core quota increase so that you can deploy clusters, which match your data processing requirements.
15+
16+
When you reach a quota limit, you can't deploy new clusters or scale out existing clusters by adding more worker nodes. The only quota limit is the CPU Cores quota that exists at the region level for each subscription. For example, your subscription may have a 30 CPU core limit in the East US region, with another 30 CPU cores allowed in the East US 2.
17+
18+
## Gather required information
19+
20+
If you have received a error indicating that you have hit a quota limit, use the process described in this section to gather important information and submit a quota increase request.
21+
22+
1. Determine your desired cluster VM size, scale, and type.
23+
1. Check the current quota capacity limits of your subscription. To check your available cores, do the following steps:
24+
25+
1. Sign in to the [Azure portal](https://portal.azure.com/).
26+
1. Navigate to the **Overview** page for the HDInsight cluster.
27+
1. On the left menu, select **Quota limits**. The page displays the number of cores in use, the number of available cores, and the total cores.
28+
29+
To request a quota increase, do the following steps:
30+
31+
1. Sign in to the [Azure portal](https://portal.azure.com/).
32+
1. Select **Help + support** on the bottom-left side of the page.
33+
34+
![help and support button](./media/quota-increase-request/help-support-button.png)
35+
36+
1. Select **New support request**.
37+
1. On the **New support request** page, under **Basics** tab, select the following options:
38+
39+
- **Issue type**: **Service and subscription limits (quotas)**
40+
- **Subscription**: the subscription you want to modify
41+
- **Quota type**: **HDInsight**
42+
43+
![Create a support request to increase HDInsight core quota](./media/quota-increase-request/hdinsight-quota-support-request.png)
44+
45+
1. Select **Next: Solutions >>**.
46+
1. On the **Details** page, enter a description of the issue, select the severity of the issue, your preferred contact method, and other required fields. Use the template listed below, to ensure that you provide necessary information. Quota increase requests are evaluated by the Azure capacity team, and not by the HDInsight product team. The more complete information you provide, the more likely your request will be approved.
47+
48+
```
49+
I would like to request [SPECIFY DESIRED AMOUNT] on [DESIRED SKU] for [SUBSCRIPTION ID].
50+
51+
My current quota on this subscription is [CURRENT QUOTA AMOUNT].
52+
53+
I would like to use the extra cores for [DETAIL REASON].
54+
```
55+
56+
![problem details](./media/quota-increase-request/problem-details.png)
57+
58+
1. Select **Next: Review + create >>**.
59+
1. On the **Review + create** tab, select **Create**.
60+
61+
> [!NOTE]
62+
> If you need to increase the HDInsight core quota in a private region, [submit a whitelist request](https://aka.ms/canaryintwhitelist).
63+
64+
You can [contact support to request a quota increase](https://docs.microsoft.com/azure/azure-portal/supportability/resource-manager-core-quotas-request).
65+
66+
There are some fixed quota limits. For example, a single Azure subscription can have at most 10,000 cores. For details on these limits, see [Azure subscription and service limits, quotas, and constraints](https://docs.microsoft.com/azure/azure-resource-manager/management/azure-subscription-service-limits).
67+
68+
## Next steps
69+
70+
* [Set up clusters in HDInsight with Apache Hadoop, Spark, Kafka, and more](hdinsight-hadoop-provision-linux-clusters.md): Learn how to set up and configure clusters in HDInsight.
71+
* [Monitor cluster performance](hdinsight-key-scenarios-to-monitor.md): Learn about key scenarios to monitor for your HDInsight cluster that might affect your cluster's capacity.

0 commit comments

Comments
 (0)