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: 

Instances are not being terminated in time (extra AWS costs)

mroy
New Contributor III

For a few days we have been trying to figure out why our AWS costs suddenly went up around March 20th, and we just found the answer: the EC2 instances are left in an unterminated state for a couple of minutes at the end of each run! 😱

This is a very serious bug, and I'm sure we're not the only customers being affected by this. 💸

We have many jobs which run very often (every 15 minutes, 30 minutes, hourly, etc.), and all of these incur an extra cost because of this bug (more than double the cost in some cases). It affects all jobs, but the impact is much less for those which run less often.

This screenshot is very explicit (y axis is the costs). It is from Cloudability, which we use to manage our AWS costs.

mroy_0-1712023586396.png

Please fix this!

1 ACCEPTED SOLUTION

Accepted Solutions

mroy
New Contributor III

Nevermind, this was actually due to a reservation that expired. 🤦‍

View solution in original post

1 REPLY 1

mroy
New Contributor III

Nevermind, this was actually due to a reservation that expired. 🤦‍

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!