实例池 APIInstance Pools API

利用实例池 API,可以创建、编辑、删除和列出实例池。The Instance Pools API allows you to create, edit, delete and list instance pools.

实例池通过维护一组空闲的随时可用的云实例来减少群集启动和自动缩放的时间。An instance pool reduces cluster start and auto-scaling times by maintaining a set of idle, ready-to-use cloud instances. 如果附加到池的群集需要一个实例,它首先会尝试分配池中的一个空闲实例。When a cluster attached to a pool needs an instance, it first attempts to allocate one of the pool’s idle instances. 如果池中没有空闲实例,则该池会通过从实例提供程序分配新的实例进行扩展,以满足群集的请求。If the pool has no idle instances, it expands by allocating a new instance from the instance provider in order to accommodate the cluster’s request. 当群集释放了某个实例时,该实例将返回到池中,以供其他群集使用。When a cluster releases an instance, it returns to the pool and is free for another cluster to use. 只有附加到池的群集才能使用该池的空闲实例。Only clusters attached to a pool can use that pool’s idle instances.

当实例在池中处于空闲状态时,Azure Databricks 不会收取 DBU 费用,Azure Databricks does not charge DBUs while instances are idle in the pool. 但这会产生实例提供程序费用,具体请参阅定价Instance provider billing does apply; see pricing.

重要

要访问 Databricks REST API,必须进行身份验证To access Databricks REST APIs, you must authenticate.

创建 Create

端点Endpoint HTTP 方法HTTP Method
2.0/instance-pools/create POST

创建实例池。Create an instance pool. 使用返回的 instance_pool_id 来查询实例池的状态,其中包括池当前分配的实例数。Use the returned instance_pool_id to query the status of the instance pool, which includes the number of instances currently allocated by the pool. 如果提供了 min_idle_instances 参数,实例会在后台进行预配,在 InstancePoolStats 中的 idle_count 等于已请求的最小值后即可使用。If you provide the min_idle_instances parameter, instances are provisioned in the background and are ready to use once the idle_count in the InstancePoolStats equals the requested minimum.

备注

由于实例提供程序限制或暂时性的网络问题,Azure Databricks 可能无法获取一些已请求的空闲实例。Azure Databricks may not be able to acquire some of the requested idle instances due to instance provider limitations or transient network issues. 群集仍可附加到实例池,但可能无法像原来那样快速启动。Clusters can still attach to the instance pool, but may not start as quickly.

示例请求:An example request:

{
  "instance_pool_name": "my-pool",
  "node_type_id": "Standard_D3_v2",
  "min_idle_instances": 10
}

响应:And response:

{
  "instance_pool_id": "0101-120000-brick1-pool-ABCD1234"
}

请求结构 Request structure

字段名称Field Name 类型Type 描述Description
instance_pool_nameinstance_pool_name STRING 实例池的名称。The name of the instance pool. 这是执行创建和编辑操作所必需的。This is required for create and edit operations. 它必须独一无二、非空且少于 100 个字符。It must be unique, non-empty, and less than 100 characters.
min_idle_instancesmin_idle_instances INT32 由池维护的空闲实例的最小数目。The minimum number of idle instances maintained by the pool. 这是对活动群集正在使用的任何实例的补充。This is in addition to any instances in use by active clusters.
max_capacitymax_capacity INT32 池可以包含的实例的最大数目,包括空闲实例数和群集正在使用的实例数。The maximum number of instances the pool can contain, including both idle instances and ones in use by clusters. 达到最大容量后,你将无法通过该池创建新的群集,并且现有的群集将无法自动纵向扩展,直到通过群集终止或纵向缩减操作让池中的某些实例进入空闲状态。Once the maximum capacity is reached, you cannot create new clusters from the pool and existing clusters cannot autoscale up until some instances are made idle in the pool via cluster termination or down-scaling.
node_type_idnode_type_id STRING 池中实例的节点类型。The node type for the instances in the pool. 附加到池的所有群集都继承此节点类型,池的空闲实例根据此类型进行分配。All clusters attached to the pool inherit this node type and the pool’s idle instances are allocated based on this type. 可以使用列出节点类型 API 调用来检索可用节点类型的列表。You can retrieve a list of available node types by using the List node types API call.
custom_tagscustom_tags ClusterTag 的数组An array of ClusterTag 实例池资源的其他标记。Additional tags for instance pool resources. Azure Databricks 会使用这些标记以及 default_tags 来标记所有的池资源(例如,VM 磁盘卷)。Azure Databricks tags all pool resources (e.g. VM disk volumes) with these tags in addition to default_tags.

Azure Databricks 最多允许 41 个自定义标记。Azure Databricks allows up to 41 custom tags.
idle_instance_autotermination_minutesidle_instance_autotermination_minutes INT32 超出 min_idle_instances 的空闲实例在被终止之前由池维护的分钟数。The number of minutes that idle instances in excess of the min_idle_instances are maintained by the pool before being terminated. 如果未指定此项,则会在默认的超时期限过后自动终止额外的空闲实例。If not specified, excess idle instances are terminated automatically after a default timeout period. 如果指定此项,则时间必须在 0 到 10000 分钟之间。If specified, the time must be between 0 and 10000 minutes. 如果提供 0,系统会尽快删除多余的空闲实例。If 0 is supplied, excess idle instances are removed as soon as possible.
enable_elastic_diskenable_elastic_disk BOOL 自动缩放本地存储:启用后,池中的实例在磁盘空间不足时会动态获取更多磁盘空间。Autoscaling Local Storage: when enabled, the instances in the pool dynamically acquire additional disk space when they are running low on disk space.
disk_specdisk_spec DiskSpecDiskSpec 定义附加到池中每个实例的初始远程存储的容量。Defines the amount of initial remote storage attached to each instance in the pool.
preloaded_spark_versionspreloaded_spark_versions 一个由 STRING 构成的数组An array of STRING 一个列表,其中包含池最多在每个实例上安装一个的运行时版本。A list with at most one runtime version the pool installs on each instance. 使用预先加载的运行时版本的池群集启动速度更快,因为不需等待映像下载。Pool clusters that use a preloaded runtime version start faster as they do have to wait for the image to download. 可以通过使用运行时版本 API 调用来检索可用的运行时版本的列表。You can retrieve a list of available runtime versions by using the Runtime versions API call.

响应结构 Response structure

字段名称Field Name 类型Type 描述Description
instance_pool_idinstance_pool_id STRING 已创建的实例池的 ID。The ID of the created instance pool.

编辑 Edit

端点Endpoint HTTP 方法HTTP Method
2.0/instance-pools/edit POST

编辑实例池。Edit an instance pool. 这会修改现有实例池的配置。This modifies the configuration of an existing instance pool.

备注

  • 仅可编辑以下字段:instance_pool_namemin_idle_instancesmax_capacityidle_instance_autotermination_minutesYou can edit only the following fields: instance_pool_name, min_idle_instances, max_capacity, and idle_instance_autotermination_minutes.
  • 必须提供 instance_pool_nameYou must supply an instance_pool_name.
  • 必须提供 node_type_id,并且它必须与原始 node_type_id 匹配。You must supply a node_type_id and it must match the original node_type_id.

示例请求:An example request:

{
  "instance_pool_id": "0101-120000-brick1-pool-ABCD1234",
  "instance_pool_name": "my-edited-pool",
  "node_type_id": "Standard_D3_v2",
  "min_idle_instances": 5,
  "max_capacity": 200,
  "idle_instance_autotermination_minutes": 30
}

请求结构 Request structure

字段名称Field Name 类型Type 描述Description
instance_pool_idinstance_pool_id STRING 要编辑的实例池的 ID。The ID of the instance pool to edit. 此字段为必需字段。This field is required.
instance_pool_nameinstance_pool_name STRING 实例池的名称。The name of the instance pool. 这是执行创建和编辑操作所必需的。This is required for create and edit operations. 它必须独一无二、非空且少于 100 个字符。It must be unique, non-empty, and less than 100 characters.
min_idle_instancesmin_idle_instances INT32 由池维护的空闲实例的最小数目。The minimum number of idle instances maintained by the pool. 这是对活动群集正在使用的任何实例的补充。This is in addition to any instances in use by active clusters.
max_capacitymax_capacity INT32 池可以包含的实例的最大数目,包括空闲实例数和群集正在使用的实例数。The maximum number of instances the pool can contain, including both idle instances and ones in use by clusters. 达到最大容量后,你将无法通过该池创建新的群集,并且现有的群集将无法自动纵向扩展,直到通过群集终止或纵向缩减操作让池中的某些实例进入空闲状态。Once the maximum capacity is reached, you cannot create new clusters from the pool and existing clusters cannot autoscale up until some instances are made idle in the pool via cluster termination or down-scaling.
node_type_idnode_type_id STRING 池中实例的节点类型。The node type for the instances in the pool. 附加到池的所有群集都继承此节点类型,池的空闲实例根据此类型进行分配。All clusters attached to the pool inherit this node type and the pool’s idle instances are allocated based on this type. 可以使用列出节点类型 API 调用来检索可用节点类型的列表。You can retrieve a list of available node types by using the List node types API call.
idle_instance_autotermination_minutesidle_instance_autotermination_minutes INT32 超出 min_idle_instances 的空闲实例在被终止之前由池维护的分钟数。The number of minutes that idle instances in excess of the min_idle_instances are maintained by the pool before being terminated. 如果未指定此项,则会在默认的超时期限过后自动终止额外的空闲实例。If not specified, excess idle instances are terminated automatically after a default timeout period. 如果指定此项,则时间必须在 0 到 10000 分钟之间。If specified, the time must be between 0 and 10000 minutes. 如果提供 0,系统会尽快删除多余的空闲实例。If 0 is supplied, excess idle instances are removed as soon as possible.

删除 Delete

端点Endpoint HTTP 方法HTTP Method
2.0/instance-pools/delete POST

删除实例池。Delete an instance pool. 这会永久删除实例池。This permanently deletes the instance pool. 池中的空闲实例会被异步终止。The idle instances in the pool are terminated asynchronously. 新群集无法附加到池。New clusters cannot attach to the pool. 附加到池的处于运行状态的群集会继续运行,但无法自动纵向扩展。Running clusters attached to the pool continue to run but cannot autoscale up. 附加到池的已终止群集将无法启动,除非将其编辑为不再使用池。Terminated clusters attached to the pool will fail to start until they are edited to no longer use the pool.

示例请求:An example request:

{
  "instance_pool_id": "0101-120000-brick1-pool-ABCD1234"
}

请求结构 Request structure

字段名称Field Name 类型Type 描述Description
instance_pool_idinstance_pool_id STRING 要删除的实例池的 ID。The ID of the instance pool to delete.

获取 Get

端点Endpoint HTTP 方法HTTP Method
2.0/instance-pools/get GET

根据标识符检索实例池的信息。Retrieve the information for an instance pool given its identifier.

示例请求:An example request:

/instance-pools/get?instance_pool_id=0101-120000-brick1-pool-ABCD1234

示例响应:An example response:

{
  "instance_pool_name": "mypool",
  "node_type_id": "Standard_D3_v2",
  "idle_instance_autotermination_minutes": 60,
  "enable_elastic_disk": false,
  "preloaded_spark_versions": [
    "5.4.x-scala2.11"
  ],
  "instance_pool_id": "101-120000-brick1-pool-ABCD1234",
  "default_tags": {
    "Vendor": "Databricks",
    "DatabricksInstancePoolCreatorId": "100125",
    "DatabricksInstancePoolId": "101-120000-brick1-pool-ABCD1234"
  },
  "state": "ACTIVE",
  "stats": {
    "used_count": 10,
    "idle_count": 5,
    "pending_used_count": 5,
    "pending_idle_count": 5
  },
  "status": {}
}

请求结构 Request structure

字段名称Field Name 类型Type 描述Description
instance_pool_idinstance_pool_id STRING 要检索其信息的实例池。The instance pool about which to retrieve information.

响应结构 Response structure

字段名称Field Name 类型Type 描述Description
instance_pool_nameinstance_pool_name STRING 实例池的名称。The name of the instance pool. 这是执行创建和编辑操作所必需的。This is required for create and edit operations. 它必须独一无二、非空且少于 100 个字符。It must be unique, non-empty, and less than 100 characters.
min_idle_instancesmin_idle_instances INT32 由池维护的空闲实例的最小数目。The minimum number of idle instances maintained by the pool. 这是对活动群集正在使用的任何实例的补充。This is in addition to any instances in use by active clusters.
max_capacitymax_capacity INT32 池可以包含的实例的最大数目,包括空闲实例数和群集正在使用的实例数。The maximum number of instances the pool can contain, including both idle instances and ones in use by clusters. 达到最大容量后,你将无法通过该池创建新的群集,并且现有的群集将无法自动纵向扩展,直到通过群集终止或纵向缩减操作让池中的某些实例进入空闲状态。Once the maximum capacity is reached, you cannot create new clusters from the pool and existing clusters cannot autoscale up until some instances are made idle in the pool via cluster termination or down-scaling.
node_type_idnode_type_id STRING 池中实例的节点类型。The node type for the instances in the pool. 附加到池的所有群集都继承此节点类型,池的空闲实例根据此类型进行分配。All clusters attached to the pool inherit this node type and the pool’s idle instances are allocated based on this type. 可以使用列出节点类型 API 调用来检索可用节点类型的列表。You can retrieve a list of available node types by using the List node types API call.
custom_tagscustom_tags ClusterTag 的数组An array of ClusterTag 实例池资源的其他标记。Additional tags for instance pool resources. Azure Databricks 会使用这些标记以及 default_tags 来标记所有的池资源(例如,VM 磁盘卷)。Azure Databricks tags all pool resources (e.g. VM disk volumes) with these tags in addition to default_tags.

Azure Databricks 最多允许 41 个自定义标记。Azure Databricks allows up to 41 custom tags.
idle_instance_autotermination_minutesidle_instance_autotermination_minutes INT32 超出 min_idle_instances 的空闲实例在被终止之前由池维护的分钟数。The number of minutes that idle instances in excess of the min_idle_instances are maintained by the pool before being terminated. 如果未指定此项,则会在默认的超时期限过后自动终止额外的空闲实例。If not specified, excess idle instances are terminated automatically after a default timeout period. 如果指定此项,则时间必须在 0 到 10000 分钟之间。If specified, the time must be between 0 and 10000 minutes. 如果提供 0,系统会尽快删除多余的空闲实例。If 0 is supplied, excess idle instances are removed as soon as possible.
enable_elastic_diskenable_elastic_disk BOOL 自动缩放本地存储:启用后,池中的实例在磁盘空间不足时会动态获取更多磁盘空间。Autoscaling Local Storage: when enabled, the instances in the pool dynamically acquire additional disk space when they are running low on disk space.
disk_specdisk_spec DiskSpecDiskSpec 定义附加到池中每个实例的初始远程存储的容量。Defines the amount of initial remote storage attached to each instance in the pool.
preloaded_spark_versionspreloaded_spark_versions 一个由 STRING 构成的数组An array of STRING 一个列表,其中包含由池安装在每个实例上的运行时版本。A list with the runtime version the pool installs on each instance. 使用预先加载的运行时版本的池群集启动速度更快,因为不需等待映像下载。Pool clusters that use a preloaded runtime version start faster as they do have to wait for the image to download. 可以通过使用运行时版本 API 调用来检索可用的运行时版本的列表。You can retrieve a list of available runtime versions by using the Runtime versions API call.
instance_pool_idinstance_pool_id STRING 实例池的符合规范的唯一标识符。The canonical unique identifier for the instance pool.
default_tagsdefault_tags ClusterTag 的数组An array of ClusterTag 由 Azure Databricks 添加的标记(与任何 custom_tags 无关),其中包括:Tags that are added by Azure Databricks regardless of any custom_tags, including:

* 供应商:Databricks* Vendor: Databricks
* DatabricksInstancePoolCreatorId:<create_user_id>* DatabricksInstancePoolCreatorId: <create_user_id>
* DatabricksInstancePoolId:<instance_pool_id>* DatabricksInstancePoolId: <instance_pool_id>
statestate InstancePoolStateInstancePoolState 实例池的当前状态。Current state of the instance pool.
statsstats InstancePoolStatsInstancePoolStats 有关实例池使用情况的统计信息。Statistics about the usage of the instance pool.
statusstatus InstancePoolStatusInstancePoolStatus 池中已失败的挂起实例的状态。Status about failed pending instances in the pool.

列出 List

端点Endpoint HTTP 方法HTTP Method
2.0/instance-pools/list GET

列出所有实例池的信息。List information for all instance pools.

示例响应:An example response:

{
  "instance_pools": [
    {
      "instance_pool_name": "my-pool",
      "min_idle_instances": 10,
      "node_type_id": "Standard_D3_v2",
      "idle_instance_autotermination_minutes": 60,
      "instance_pool_id": "0101-120000-brick1-pool-ABCD1234",
      "default_tags": [
        { "DatabricksInstancePoolCreatorId", "1234" },
        { "DatabricksInstancePoolId", "0101-120000-brick1-pool-ABCD1234" }
      ],
      "stats": {
        "used_count": 10,
        "idle_count": 5,
        "pending_used_count": 5,
        "pending_idle_count": 5
      }
    }
  ]
}

响应结构 Response structure

字段名称Field Name 类型Type 描述Description
instance_poolsinstance_pools InstancePoolAndStats 的数组An array of InstancePoolAndStats 实例池的列表,其中包含实例池的统计信息。A list of instance pools with their statistics included.

数据结构 Data structures

本节内容:In this section:

InstancePoolState InstancePoolState

实例池的状态。The state of an instance pool. 当前允许的状态转换为:The current allowable state transitions are:

  • ACTIVE -> DELETED
名称Name 描述Description
ACTIVEACTIVE 指示实例池处于活动状态。Indicates an instance pool is active. 群集可以附加到该实例池。Clusters can attach to it.
DELETEDDELETED 指示实例池已被删除,不再可供访问。Indicates the instance pool has been deleted and is no longer accessible.

InstancePoolStats InstancePoolStats

有关实例池使用情况的统计信息。Statistics about the usage of the instance pool.

字段名称Field Name 类型Type 描述Description
used_countused_count INT32 群集正在使用的活动实例数。Number of active instances that are in use by a cluster.
idle_countidle_count INT32 群集未在使用的活动实例数。Number of active instances that are not in use by a cluster.
pending_used_countpending_used_count INT32 分配给群集的挂起实例数。Number of pending instances that are assigned to a cluster.
pending_idle_countpending_idle_count INT32 未分配给群集的挂起实例数。Number of pending instances that are not assigned to a cluster.

InstancePoolStatus InstancePoolStatus

池中已失败的挂起实例的状态。Status about failed pending instances in the pool.

字段名称Field Name 类型Type 描述Description
pending_instance_errorspending_instance_errors PendingInstanceError 的数组An array of PendingInstanceError 失败的挂起实例的错误消息列表。List of error messages for the failed pending instances.

PendingInstanceError PendingInstanceError

失败的挂起实例的错误消息。Error message of a failed pending instance.

字段名称Field Name 类型Type 描述Description
instance_idinstance_id STRING 失败实例的 ID。ID of the failed instance.
messagemessage STRING 描述失败原因的消息。Message describing the cause of the failure.

DiskSpec DiskSpec

描述要附加到每个实例的初始磁盘集。Describes the initial set of disks to attach to each instance. 例如,如果有 3 个实例,一开始为每个实例配置 2 个磁盘,每个磁盘 100 GiB,则 Azure Databricks 为这些实例总共创建 6 个磁盘,每个磁盘 100 GiB。For example, if there are 3 instances and each instance is configured to start with 2 disks, 100 GiB each, then Azure Databricks creates a total of 6 disks, 100 GiB each, for these instances.

字段名称Field Name 类型Type 描述Description
disk_typedisk_type DiskTypeDiskType 要附加的磁盘的类型。The type of disks to attach.
disk_countdisk_count INT32 要附加到每个实例的磁盘数:The number of disks to attach to each instance:

* 只会为支持的节点类型启用此功能。* This feature is only enabled for supported node types.
* 用户可以选择的磁盘数量不能超过节点类型支持的磁盘数量上限。* Users can choose up to the limit of the disks supported by the node type.
* 对于不带本地磁盘的节点类型,需要指定至少一个磁盘。* For node types with no local disk, at least one disk needs to be specified.
disk_sizedisk_size INT32 要附加的每个磁盘的大小(以 GiB 为单位)。The size of each disk (in GiB) to attach. 值必须在特定实例类型支持的范围内:Values must fall into the supported range for a particular instance type:

* 高级 LRS (SSD):1 - 1023 GiB* Premium LRS (SSD): 1 - 1023 GiB
* 标准 LRS (HDD):1- 1023 GiB* Standard LRS (HDD): 1- 1023 GiB

DiskType DiskType

描述磁盘的类型。Describes the type of disk.

字段名称Field Name 类型Type 描述Description
azure_disk_volume_typeazure_disk_volume_type AzureDiskVolumeTypeAzureDiskVolumeType 要使用的 Azure 磁盘的类型。The type of Azure disk to use.

InstancePoolAndStats InstancePoolAndStats

字段名称Field Name 类型Type 描述Description
instance_pool_nameinstance_pool_name STRING 实例池的名称。The name of the instance pool. 这是执行创建和编辑操作所必需的。This is required for create and edit operations. 它必须独一无二、非空且少于 100 个字符。It must be unique, non-empty, and less than 100 characters.
min_idle_instancesmin_idle_instances INT32 由池维护的空闲实例的最小数目。The minimum number of idle instances maintained by the pool. 这是对活动群集正在使用的任何实例的补充。This is in addition to any instances in use by active clusters.
max_capacitymax_capacity INT32 池可以包含的实例的最大数目,包括空闲实例数和群集正在使用的实例数。The maximum number of instances the pool can contain, including both idle instances and ones in use by clusters. 达到最大容量后,你将无法通过该池创建新的群集,并且现有的群集将无法自动纵向扩展,直到通过群集终止或纵向缩减操作让池中的某些实例进入空闲状态。Once the maximum capacity is reached, you cannot create new clusters from the pool and existing clusters cannot autoscale up until some instances are made idle in the pool via cluster termination or down-scaling.
node_type_idnode_type_id STRING 池中实例的节点类型。The node type for the instances in the pool. 附加到池的所有群集都继承此节点类型,池的空闲实例根据此类型进行分配。All clusters attached to the pool inherit this node type and the pool’s idle instances are allocated based on this type. 可以使用列出节点类型 API 调用来检索可用节点类型的列表。You can retrieve a list of available node types by using the List node types API call.
custom_tagscustom_tags ClusterTag 的数组An array of ClusterTag 实例池资源的其他标记。Additional tags for instance pool resources. Azure Databricks 会使用这些标记以及 default_tags 来标记所有的池资源(例如,VM 磁盘卷)。Azure Databricks tags all pool resources (e.g. VM disk volumes) with these tags in addition to default_tags.

Azure Databricks 最多允许 41 个自定义标记。Azure Databricks allows up to 41 custom tags.
idle_instance_autotermination_minutesidle_instance_autotermination_minutes INT32 超出 min_idle_instances 的空闲实例在被终止之前由池维护的分钟数。The number of minutes that idle instances in excess of the min_idle_instances are maintained by the pool before being terminated. 如果未指定此项,则会在默认的超时期限过后自动终止额外的空闲实例。If not specified, excess idle instances are terminated automatically after a default timeout period. 如果指定此项,则时间必须在 0 到 10000 分钟之间。If specified, the time must be between 0 and 10000 minutes. 如果提供 0,系统会尽快删除多余的空闲实例。If 0 is supplied, excess idle instances are removed as soon as possible.
enable_elastic_diskenable_elastic_disk BOOL 自动缩放本地存储:启用后,池中的实例在磁盘空间不足时会动态获取更多磁盘空间。Autoscaling Local Storage: when enabled, the instances in the pool dynamically acquire additional disk space when they are running low on disk space.
disk_specdisk_spec DiskSpecDiskSpec 定义附加到池中每个实例的初始远程存储的容量。Defines the amount of initial remote storage attached to each instance in the pool.
preloaded_spark_versionspreloaded_spark_versions 一个由 STRING 构成的数组An array of STRING 一个列表,其中包含由池安装在每个实例上的运行时版本。A list with the runtime version the pool installs on each instance. 使用预先加载的运行时版本的池群集启动速度更快,因为不需等待映像下载。Pool clusters that use a preloaded runtime version start faster as they do have to wait for the image to download. 可以通过使用运行时版本 API 调用来检索可用的运行时版本的列表。You can retrieve a list of available runtime versions by using the Runtime versions API call.
instance_pool_idinstance_pool_id STRING 实例池的符合规范的唯一标识符。The canonical unique identifier for the instance pool.
default_tagsdefault_tags ClusterTag 的数组An array of ClusterTag 由 Azure Databricks 添加的标记(与任何 custom_tags 无关),其中包括:Tags that are added by Azure Databricks regardless of any custom_tags, including:

* 供应商:Databricks* Vendor: Databricks
* DatabricksInstancePoolCreatorId:<create_user_id>* DatabricksInstancePoolCreatorId: <create_user_id>
* DatabricksInstancePoolId:<instance_pool_id>* DatabricksInstancePoolId: <instance_pool_id>
statestate InstancePoolStateInstancePoolState 实例池的当前状态。Current state of the instance pool.
statsstats InstancePoolStatsInstancePoolStats 有关实例池使用情况的统计信息。Statistics about the usage of the instance pool.

AzureDiskVolumeType AzureDiskVolumeType

Azure Databricks 支持的所有 Azure 磁盘类型。All Azure Disk types that Azure Databricks supports. 请参阅 /virtual-machines/linux/disks-typesSee /virtual-machines/linux/disks-types

名称Name 描述Description
PREMIUM_LRSPREMIUM_LRS SSD 支持的高级存储层。Premium storage tier, backed by SSDs.
STANDARD_LRSSTANDARD_LRS HDD 支持的标准存储层。Standard storage tier, backed by HDDs.