# Missing Auto-Termination Policy for Databricks Clusters

Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/missing-auto-termination-policy-for-databricks-clusters

[Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) 

# Missing Auto-Termination Policy for Databricks Clusters

## Explanation

In many environments, users launch Databricks clusters for development or analysis and forget to shut them down after use. 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.

## Relevant Billing Model

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.

## Detection

- 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

## Remediation

- 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

## Relevant Documentation

[Submit Feedback](https://hub.pointfive.co/inefficiencies/missing-auto-termination-policy-for-databricks-clusters)

## At a glance

Reference

CER-0022

Cloud provider

Databricks

Service

Databricks Clusters

Category

[Compute](https://www.pointfive.co/efficiency-hub/service-category/compute)

Inefficiency type

Missing Safeguard

## Contributed by

- Jason Eckle 

### Jason Eckle

Manager Cloud FinOps @ Etsy

[LinkedIn](https://www.linkedin.com/in/jasoneckle/)

---
Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.