Skip to content

Commit a2c6359

Browse files
Merge pull request #220510 from vijetajo/patch-110
Update how-to-create-attach-compute-cluster.md
2 parents 0f5654a + d5b71e4 commit a2c6359

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

articles/machine-learning/how-to-create-attach-compute-cluster.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -63,9 +63,6 @@ Compute clusters can run jobs securely in a [virtual network environment](how-to
6363

6464
* Azure allows you to place _locks_ on resources, so that they can't be deleted or are read only. __Do not apply resource locks to the resource group that contains your workspace__. Applying a lock to the resource group that contains your workspace will prevent scaling operations for Azure ML compute clusters. For more information on locking resources, see [Lock resources to prevent unexpected changes](../azure-resource-manager/management/lock-resources.md).
6565

66-
> [!TIP]
67-
> Clusters can generally scale up to 100 nodes as long as you have enough quota for the number of cores required. By default clusters are setup with inter-node communication enabled between the nodes of the cluster to support MPI jobs for example. However you can scale your clusters to 1000s of nodes by simply [raising a support ticket](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest), and requesting to allow list your subscription, or workspace, or a specific cluster for disabling inter-node communication.
68-
6966
## Create
7067

7168
**Time estimate**: Approximately 5 minutes.

0 commit comments

Comments
 (0)