Skip to content

Commit

Permalink
[Doc] clarified spot_bid_max_price option for databricks_cluster (#…
Browse files Browse the repository at this point in the history
…3830)

## Changes
- Resolves #3744

## Tests
<!-- 
How is this tested? Please see the checklist below and also describe any
other relevant tests
-->

- [x] relevant change in `docs/` folder
  • Loading branch information
nkvuong authored Jul 29, 2024
1 parent 7825dd7 commit 1a309c8
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 3 deletions.
3 changes: 1 addition & 2 deletions docs/resources/cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -201,7 +201,6 @@ library {

Installing Python libraries listed in the `requirements.txt` file. Only Workspace paths and Unity Catalog Volumes paths are supported. Requires a cluster with DBR 15.0+.


```hcl
library {
requirements = "/Workspace/path/to/requirements.txt"
Expand Down Expand Up @@ -414,7 +413,7 @@ The following options are [available](https://docs.microsoft.com/en-us/azure/dat

* `availability` - (Optional) Availability type used for all subsequent nodes past the `first_on_demand` ones. Valid values are `SPOT_AZURE`, `SPOT_WITH_FALLBACK_AZURE`, and `ON_DEMAND_AZURE`. Note: If `first_on_demand` is zero, this availability type will be used for the entire cluster.
* `first_on_demand` - (Optional) The first `first_on_demand` nodes of the cluster will be placed on on-demand instances. If this value is greater than 0, the cluster driver node will be placed on an on-demand instance. If this value is greater than or equal to the current cluster size, all nodes will be placed on on-demand instances. If this value is less than the current cluster size, `first_on_demand` nodes will be placed on on-demand instances, and the remainder will be placed on availability instances. This value does not affect cluster size and cannot be mutated over the lifetime of a cluster.
* `spot_bid_max_price` - (Optional) The max price for Azure spot instances. Use `-1` to specify the lowest price.
* `spot_bid_max_price` - (Optional) The max bid price used for Azure spot instances. You can set this to greater than or equal to the current spot price. You can also set this to `-1`, which specifies that the instance cannot be evicted on the basis of price. The price for the instance will be the current price for spot instances or the price for a standard instance.

### gcp_attributes

Expand Down
2 changes: 1 addition & 1 deletion docs/resources/instance_pool.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@ The following options are [available](https://docs.databricks.com/dev-tools/api/
The following options are [available](https://docs.microsoft.com/en-us/azure/databricks/dev-tools/api/latest/clusters#--azureattributes):

* `availability` - (Optional) Availability type used for all nodes. Valid values are `SPOT_AZURE` and `ON_DEMAND_AZURE`.
* `spot_bid_max_price` - (Optional) The max price for Azure spot instances. Use `-1` to specify the lowest price.
* `spot_bid_max_price` - (Optional) The max bid price used for Azure spot instances. You can set this to greater than or equal to the current spot price. You can also set this to `-1`, which specifies that the instance cannot be evicted on the basis of price. The price for the instance will be the current price for spot instances or the price for a standard instance.

### gcp_attributes Configuration Block

Expand Down

0 comments on commit 1a309c8

Please sign in to comment.