集區Pools

Azure Databricks 集區會藉由維護一組閒置、立即可用的執行個體,來減少叢集啟動和自動調整的時間。Azure Databricks pools reduce cluster start and auto-scaling times by maintaining a set of idle, ready-to-use 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, the pool 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 不會在執行個體於集區中閒置時對 Databricks 單位收費。Azure Databricks does not charge DBUs while instances are idle in the pool. 但執行個體提供者會計費;請參閱價格Instance provider billing does apply; see pricing.

您可以使用 UI、CLI 和藉由叫用集區 API 來管理集區。You can manage pools using the UI, the CLI, and by invoking the Pools API. 本節會說明如何使用 UI 來處理集區。This section describes how to work with pools using the UI. 如需其他方法,請參閱執行個體集區 CLI執行個體集區 APIFor the other methods, see Instance Pools CLI and Instance Pools API.

本節內容:In this section: