Platform release process

In order to minimize disruption to Databricks users, releases are deployed on a regular cadence. During a deployment, Databricks services may be temporarily disrupted.

Release deployments are scheduled outside of normal business hours for the region in which they occur.

Notification types

There are multiple types of notifications that appear before a deployment starts, depending on your deployment model.

The following sections highlight the most common methods.

Status Page

Before a deployment begins, the Databricks Status Page is updated to indicate the impacted regions.

When a deployment ends, the Databricks Status Page is updated to show normal operation.

Status Page automatic notification

If you have subscribed to automatic notifications, you will receive an alert before a deployment begins, and then a second alert when the deployment has concluded. These can be via email or webhook, depending on the subscription type you have configured.

Example email notification

The following is an example email notification that is sent to subscribers when a scheduled deployment begins.

Title: Maintenance Notification from Databricks

Affected Infrastructure
Components: Authentication, Compute Service, Jobs Service, ODBC/JDBC Service, User Interface,API Service
Locations: eu:europe-west2:EU-West2

Update:
Databricks has initiated scheduled maintenance in the listed regions. Review the release notes for more information on recent platform updates. An additional notification will be sent when maintenance is completed.