Hi Suki Azure,
Stopping the cluster before enabling Spot instances for the Databricks VM is the right approach, the underlying VM might still be retained by Azure for a while even after the cluster is stopped. Here are a few things to verify:
- Make sure the cluster is fully terminated before restarting it with Spot enabled.
- When editing the cluster, ensure that Spot instances are explicitly selected in the worker type settings.
- You can also check the Azure Resource Explorer to confirm if the Spot policy is applied at the VM scale set level.
If the Spot option is still not reflecting, you might need to create a new cluster from scratch with Spot enabled right from the start.
For the Windows Jump Host, unfortunately, you can’t convert an existing VM to a Spot VM directly. You need to recreate it, but you can definitely capture an image of your current VM and use that to deploy the new one:
- Go to the Azure portal, navigate to your VM, and use the Capture Image option.
- Store the image in an Azure Compute Gallery or as a managed image.
- Create a new Spot VM using that image.
Remember that Spot VMs can be evicted at any time. So, if it’s a critical workload, you may want to have a backup plan in place.
Please refer the document below:
https://learn.microsoft.com/en-us/azure/virtual-machines/spot-vms
https://learn.microsoft.com/en-us/azure/virtual-machines/spot-portal
If you found the information helpful, please click "Upvote" on the post to let us know.
Thank You,