Deployment set routing #

Starburst Galaxy can handle spikes in workload demand by autoscaling a cluster, but a single cluster still has finite processing capacity. If a cluster becomes overwhelmed with concurrent workloads, you might experience performance degradation and slower response times, even with autoscaling enabled.

To handle this type of heavy demand on a cluster, you can use deployment set routing. Deployment set routing launches multiple Trino deployments as replicated clusters. Replicas are identical to the original cluster, use the same cluster URL, and do not need to be manually managed. When you create one or more replicated clusters, Galaxy routes queries across multiple coordinators to distribute a heavy workload. Automated load balancing ensures that no single cluster becomes overwhelmed.

You can use deployment set routing alone, or in combination with user role-based routing. No changes to routing rules are required. You can create up to eight replicated clusters, either when you create a new cluster or edit an existing cluster.

Limitations #

The limitations of deployment set routing are:

• Auto-suspending is not supported. By extension, cluster schedules are not supported.
• Autoscaling is not supported.
• OpenTelemetry APIs are not supported.
• The Trino UI is not supported.