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: 

Multiple orphan vms in managed resource group after starting and terminating my personal cluster

milicevica
New Contributor

Hi today, i had problem with starting the cluster and therefore i did multiple times star and terminating. The problem is that this actions always started one new VM in the managed resource group but never turned it off. Therefore i ended up with multiple orphans vms which i cant stop or delete. 

Is there a ways to stop those machines? Does somebody have the same problem?

 

Br, 

Aleksandar

1 ACCEPTED SOLUTION

Accepted Solutions

daniel_sahal
Esteemed Contributor

@milicevica 
I'm not sure if we'll be able to help here.
Simply raise a ticket to your cloud vendor.

View solution in original post

2 REPLIES 2

daniel_sahal
Esteemed Contributor

@milicevica 
I'm not sure if we'll be able to help here.
Simply raise a ticket to your cloud vendor.

Hubert-Dudek
Esteemed Contributor III

It always takes a few minutes, even 10, before the machine is terminated in Azure. It is better to set a pool of machines in data bricks and use them from there so we will not be keeping Zombie machines.

Join 100K+ Data Experts: Register Now & Grow with Us!

Excited to expand your horizons with us? Click here to Register and begin your journey to success!

Already a member? Login and join your local regional user group! If there isn’t one near you, fill out this form and we’ll create one for you to join!