cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
Administration & Architecture
Explore discussions on Databricks administration, deployment strategies, and architectural best practices. Connect with administrators and architects to optimize your Databricks environment for performance, scalability, and security.
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

Can't create AWS p3 instance

168793
New Contributor II

Hi, I'm trying to create a `p3.2xlarge` in my workspace, but the cluster fails to instantiate, specifically getting this error message: `No zone supports both the driver instance type [p3.2xlarge] and the worker instance type [p3.2xlarge]` (though I am just creating a Single Node instance). I can create other clusters with other GPU instance types (eg, g6 class).

I can confirm that I have Limit capacity for P instances (76 vCPUs in the region, us-east-1). Does anyone have any clues on how I can debug this issue?

4 REPLIES 4

Walter_C
Databricks Employee
Databricks Employee

Can you please share the complete error showed in the event logs when trying to run the cluster? does the availability zone available have the capacity for this instances?

168793
New Contributor II

Here is an example (this was when I tried a `p3.8xlarge`, and I set the Availability Zone = Auto for the cluster)

```In zone us-east-1c, insufficient capacity for the following node type: p3.8xlarge. AWS Error: Failure happened when talking to AWS, AWS API error code: Unsupported AWS error message: Your requested instance type (p3.8xlarge) is not supported in your requested Availability Zone (us-east-1c). Please retry your request by not specifying an Availability Zone or choosing us-east-1a, us-east-1d, us-east-1e, us-east-1f. In zone us-east-1d, insufficient capacity for the following node type: p3.8xlarge. AWS Error: Failure happened when talking to AWS, AWS API error code: Unsupported AWS error message: Your requested instance type (p3.8xlarge) is not supported in your requested Availability Zone (us-east-1d). Please retry your request by not specifying an Availability Zone or choosing us-east-1a, us-east-1e, us-east-1f.```

The odd thing is it gives that message once, and then just gives a more succinct message in the Event Log: `No zone supports both the driver instance type [p3.8xlarge] and the worker instance type [p3.8xlarge]` afterwards. And every time I try to start the cluster it continues with that message, as if it doesn't try again across the different AZ's. 

 

 

 

Walter_C
Databricks Employee
Databricks Employee

I tried on my internal environment setting it on us-east-1a or us-east-1b and it has worked on my side, can you try to force them to be created on any of this 2, is it the same exact issue?

tyagip1
New Contributor

Facing the same issue. Tried specifying the Availability zone as eu-west-1a, eu-west-1b and auto. But event logs throws the same error:

tyagip1_0-1735822123004.png

 

Connect with Databricks Users in Your Area

Join a Regional User Group to connect with local Databricks users. Events will be happening in your city, and you wonโ€™t want to miss the chance to attend and share knowledge.

If there isnโ€™t a group near you, start one and help create a community that brings people together.

Request a New Group