Starburst Galaxy

  •  Get started

  •  Working with data

  •  Data engineering

  •  Developer tools

  •  Cluster administration

  •  Security and compliance

  •  Troubleshooting

  • Galaxy status

  •  Reference

  • Configure autoscaling #

    Autoscaling considers combined CPU usage of running queries and estimated CPU time of running and queued queries to determine the most suitable cluster size. Autoscaling responds rapidly to workload changes by adding or removing workers and by reactivating draining worker nodes to ensure efficient resource allocation for both CPU and I/O-bound tasks.

    Get started #

    To configure autoscaling, you must have the privileges to create and edit a cluster. By default, the accountadmin role has the privileges to configure autoscaling.

    You can configure autoscaling when creating a new cluster or when editing an existing cluster.

    Configure new cluster #

    In the navigation, click Admin > Clusters.

    1. Click Create cluster. See Create a cluster for details.

    2. In the Size section, select the Autoscaling enabled checkbox to use autoscaling. This adds a second text input field and slider endpoint so you can set a minimum and maximum number of worker nodes to scale between.

    3. Click Create cluster.

    Configure existing cluster: #

    In the navigation, click Admin > Clusters.

    1. Choose an existing cluster from the clusters list and open the Edit cluster panel:

      • Click the more_vert options menu, and select Edit cluster. The Edit cluster panel should now be open.

    2. In the Size section, select the Autoscaling enabled checkbox. This adds a second text input field and slider endpoint so you can set a minimum and maximum number of worker nodes to scale between.

    3. Click Save changes.

    When to use autoscaling #

    There are many reasons to configure autoscaling on your cluster. Here are some things to consider:

    • Default cluster sizes start with the specified minimum number of workers and end with the same maximum number, regardless of whether that many workers are needed for a given query.
    • A default cluster size is better when running quick or short workloads and suspending the cluster once done.
    • Autoscaling is more efficient when workflows are large, vary over time, or are automated. This allows the cluster to adjust resource usage to the needs of the workload.

    Other useful resources: