Guide to scheduling Databricks cluster start and termination times. Reduce Databricks compute costs meaningfully by stopping idle clusters outside work hours.
This is the practical version, the one you can follow in a single sitting. It starts read-only, touches no production resource by default, and every step is reversible, so there is no point at which you are committed to something you cannot undo. Budget about 10 minutes. Before you start you will want: A Databricks workspace; API access token or service principal; A ZopNight account.
The steps
- Connect your Databricks workspace.
- Identify always-on clusters.
- Create termination schedules.
- Handle job clusters separately.
Why this is safe to do today
The reason this is a low-stakes change is that nothing here is destructive. Scheduling stops and starts resources; it never deletes them, and your data persists across a stop exactly as it does across a normal reboot. Production is excluded by default, actions run in dependency order, and every state change is logged with what triggered it.
If you want the fuller context behind this task, the FinOps guide covers where it fits, and the AWS EC2 scheduling page shows the same loop applied to a specific resource.
Getting started
Getting started is intentionally low-stakes:
- Connect your cloud provider with a read-only role. Nothing is scheduled or changed at this stage.
- Let ZopNight discover your non-production resources and review exactly what it found, filtered by account, region, and status.
- Create a schedule in your timezone and attach the non-production resources or groups you want it to cover.
- Watch the first cycle run, with Slack, Teams, or Google Chat notifications on every start, stop, and failure, then layer in idle cleanup and guided rightsizing.
Production stays excluded by default throughout, and because discovery and recommendations are read-only, you can prove the value before you enable a single action.
Questions we get a lot.
If yours isn't here, email us and we'll answer directly.
Does Databricks already auto-terminate idle clusters?
Databricks supports auto-termination after a configurable idle period, but many teams disable it for convenience. ZopNight adds time-based scheduling that stops clusters at a specific time regardless of activity, preventing overnight waste.
Will scheduling affect my Databricks notebooks?
No. Notebooks are stored in the Databricks workspace, not on the cluster. When the cluster restarts, you re-attach the notebook and continue where you left off. Running notebook state is lost, so schedule stops after your team finishes work.