# Missing auto-termination policy for Databricks clusters Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/missing-auto-termination-policy-for-databricks-clusters In many environments, users launch Databricks clusters for development or analysis and forget to shut them down after use. By: Jason Eckle Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Missing Auto-Termination Policy for Databricks Clusters The short version In many environments, users launch Databricks clusters for development or analysis and forget to shut them down after use. [Jason Eckle](https://www.linkedin.com/in/jasoneckle/) Manager Cloud FinOps @ Etsy Databricks service [Databricks Clusters](https://www.pointfive.co/efficiency-hub/cloud-services/databricks-clusters) Category [Compute](https://www.pointfive.co/efficiency-hub/service-category/compute) Reference CER-0022 Type Governance Gap ## Explanation Why the waste happens and who it affects. When no auto-termination policy is configured, these clusters remain active indefinitely, incurring unnecessary charges for both Databricks and cloud infrastructure usage. This inefficiency is especially common in interactive clusters that are user-managed, ephemeral, or exploratory in nature. While Databricks provides built-in support for cluster auto-termination, teams often overlook it unless it's enforced through workspace policies. Without this safeguard in place, idle clusters can persist unnoticed for hours or days, leading to avoidable cost. ## Billing model The pricing dimensions that drive this cost. Databricks clusters accrue cost per second through: Databricks Unit (DBU) charges Vary by workload type (interactive, job, SQL) Underlying cloud compute - billed through the host cloud provider (e.g., EC2, Azure VMs) Clusters without auto-termination continue to run - and generate cost - even if idle or abandoned. ## How to detect 4 checks to find it in your estate. - Identify clusters that do not have auto-termination enabled - Check for clusters with long idle times and no active workloads - Analyze cost reports to detect charges from underutilized or inactive clusters - Review workspace-level cluster policies and defaults to ensure consistent enforcement ## How to fix 4 ways to remove the waste. - Enable auto-termination for all clusters that do not require persistent runtime - Set cluster policies to require auto-termination configuration for new clusters - Establish reasonable inactivity thresholds based on workload type (e.g., 30-60 minutes for interactive) - Educate users on the financial impact of idle clusters and the role of auto-termination as a cost control mechanism ## Documentation Vendor references for pricing and configuration. - [Compute configuration reference docs.databricks.com](https://docs.databricks.com/aws/en/compute/configure) - [Manage classic compute docs.databricks.com](https://docs.databricks.com/aws/en/compute/clusters-manage) - [Compute policy reference docs.databricks.com](https://docs.databricks.com/aws/en/admin/clusters/policy-definition) - [Databricks Pricing databricks.com](https://www.databricks.com/product/pricing) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - Databricks Clusters CER-0098 ### [On-Demand-Only Configuration for Non-Production Databricks Clusters](https://www.pointfive.co/efficiency-hub/inefficiencies/on-demand-only-configuration-for-non-production-databricks-clusters) In non-production environments - such as development, testing, and experimentation-many teams default to on-demand nodes out of habit or caution. However, Databricks offers built-in support for using spot instances safely. Its job... Compute - Databricks Clusters CER-0159 ### [Inefficient Use of Photon Engine in Databricks Compute](https://www.pointfive.co/efficiency-hub/inefficiencies/inefficient-use-of-photon-engine-in-databricks-compute) Photon is enabled by default on many Databricks compute configurations. While it can accelerate certain SQL and DataFrame operations, its performance benefits are workload-specific and may not justify the increased DBU cost. Many... Compute - Databricks Clusters CER-0116 ### [Lack of Graviton Usage in Databricks Clusters](https://www.pointfive.co/efficiency-hub/inefficiencies/lack-of-graviton-usage-in-databricks-clusters) Databricks supports AWS Graviton-based instances for most workloads, including Spark jobs, data engineering pipelines, and interactive notebooks. These instances offer significant cost advantages over traditional x86-based VMs, with... Compute --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.