Instance pooling reduces cluster node spin-up time by maintaining a set of idle and ready instances. The
|D s platform|
- All cluster nodes used by the
are taken from the pool. If the pool has an insufficient number of nodes, cluster creation fails.
D s platform
- Each user must have access to the pool and must have at least the
- Each user must have a personal access token from the same Azure AWS Databricks workspace. See Configure personal access token below.
Acquire your pool identifier or pool name from Azure AWS Databricks.
NOTE: You can use either the Databricks pool identifier or pool name.If both poolId and poolName are specified, poolId is used first. If that fails to find a matching identifier, then the poolName value is checked.
Tip: If you specify a poolName value only, then you can run your Databricks jobs against the available clusters across multiple
. This mechanism allows for better resource allocation and broader execution options.
D s item item workspaces D s config
Set either of the following parameters:
Set the following parameter to the Azure AWS Databricks pool identifier:
Or, you can set the following parameter to the Azure AWS Databricks pool name:
- Save your changes and restart the platform.