About control plane#
Note
The previous name of the Starburst control plane was Starburst Portal.
Control plane is an optional deployment package for Starburst Enterprise platform (SEP). You use it to run SEP in a scalable single or multi-cluster deployment that you can manage from one place.
Why use control plane#
With control plane, you can run more than one cluster, or in the LakeOps use case more than one engine, behind a single endpoint. You can use several clusters to scale a deployment, to keep it available when a component fails, and to separate workloads from each other.
Control plane also provides exclusive features, such as LakeOps, that are not available with SEP alone. These features work with the centralized catalogs and Starburst access control policies that control plane manages.
What control plane provides#
One place for catalogs, access control, and query routing. You manage catalogs and access in control plane. Your users submit queries to one URL, and control plane sends each query to a cluster group using the routing rules that you configure.
Starburst access control. A role and attribute-based system of access control that you configure once on control plane, so that it applies to every cluster.
Access to LakeOps. LakeOps maintains your Iceberg tables automatically. It runs as a separate engine, and control plane gives you access to it.
Components and their status#
Component |
What it does |
Status |
|---|---|---|
Query routing |
Sends each query to a cluster group by using routing rules. |
Public preview |
Coordinator high availability |
Keeps a cluster available when its coordinator fails. |
Public preview |
Centralized catalog management |
Manages catalogs for all clusters in one place. |
Public preview |
Access control |
Starburst access control manages access to catalogs and data in one place on the control plane. Alternatively, you can delegate access control to built-in access control on the cluster. |
Public preview |
LakeOps |
Maintains Iceberg tables automatically. |
Public preview |
Query editor |
Lets you run queries from control plane. |
Public preview |
Query insights |
Shows which cluster and cluster group handled each query. |
Public preview |
Audit log |
Records the changes that administrators make in control plane, so that you can review them. |
Public preview |
Usage metrics |
Shows the usage of your clusters in one place, and lets you download the data. |
Public preview |
Lightweight Directory Access Protocol (LDAP) user and group provisioning |
Synchronizes users and groups from your LDAP servers into control plane. |
Public preview |
System for Cross-domain Identity Management (SCIM) provisioning |
Lets your identity provider create and update users and groups in control plane. |
Public preview |
Starburst Metastore |
Stores table metadata. |
GA |
Use cases#
You can use control plane for the following use cases. For an introduction to the key use cases, see Key use cases.
High availability. Keep a cluster available when its coordinator fails.
Workload isolation. Run dissimilar workloads on separate clusters, so that they do not interfere with each other.
Load balancing. Scale a workload beyond one cluster by spreading its queries across several clusters.
Centrally managed single or multi-cluster deployment. Manage connections, access, and assets for one cluster or many from control plane.
Control plane features. Use features that exist only in control plane, such as LakeOps.
You can combine use cases. For example, one deployment can use workload isolation, load balancing, and coordinator high availability together.
License requirements#
An instance of control plane provides several independent services as listed in Components and their status. For any of its component services other than Starburst Metastore, a license is required for the control plane instance and for every SEP cluster that connects to it. Contact Starburst Support for further details.
Control plane in standalone mode#
Existing control plane deployments can continue to run clusters in standalone mode, which is the mode introduced in SEP versions 480-e through 483-e. In standalone mode, control plane routes queries and monitors the status of your clusters. Each cluster is individually managed and keeps its own catalogs and built-in access control.
Important
The deployment.mode property of a SEP cluster defaults to STANDALONE. To
keep running an existing (480-e through 483-e) control plane in standalone mode,
you do not need to change this property on your clusters. However, you must set
statement-queue.enabled=false in the config.properties file of control
plane.
Standalone mode is not recommended for new deployments. It will not receive many of the new features coming to control plane in the future, and will eventually be phased out in favor of the centralized managed deployment. For details about standalone control plane, see the documentation for version 483-e.
Standalone mode supports query routing, load balancing, and coordinator high availability. It also supports the query editor, query insights, and the audit log.
Features that require catalogs and access control on the control plane, such as LakeOps, require both control plane and clusters in managed mode.
The configurations for standalone mode and managed mode vary. See Install and configure control plane for more information.