04-28-2023 03:04 AM
04-28-2023 03:19 AM
Hello @Amine HADJ-YOUCEF
“SUBNET_EXHAUSTED_FAILURE” are because VMs on unhealthy partitions cannot be freed, so the resources and associated quota cannot be released, and you are running out of quota.
Your vnet/subnet is out of non-occupied IPs and this can be fixed by allocating more IPs to your network address space.
Each cluster requires it's own IP, so if there are none available, it simply cannot start.
Hope this helps.
Thanks & Regards,
Nandini
04-28-2023 03:17 AM
#DAIS2023 i guess If your subnet is too small to accommodate all the required network interfaces, you can try increasing its size by adding more IP addresses to it.
04-28-2023 03:19 AM
Hello @Amine HADJ-YOUCEF
“SUBNET_EXHAUSTED_FAILURE” are because VMs on unhealthy partitions cannot be freed, so the resources and associated quota cannot be released, and you are running out of quota.
Your vnet/subnet is out of non-occupied IPs and this can be fixed by allocating more IPs to your network address space.
Each cluster requires it's own IP, so if there are none available, it simply cannot start.
Hope this helps.
Thanks & Regards,
Nandini
04-28-2023 03:56 AM
Are you sure you can change the subnet size on an existing Databricks environment? I was always told that this is not possible.
05-02-2023 02:43 AM
@Werner Stinckens ,
I checked again, you cannot change them after your workspace is deployed. The only way right now is to recreate the workspace and migrate. It’s not possible to update CIDR range right now without migration.
Join our fast-growing data practitioner and expert community of 80K+ members, ready to discover, help and collaborate together while making meaningful connections.
Click here to register and join today!
Engage in exciting technical discussions, join a group with your peers and meet our Featured Members.