Skip to main content

Manual Scaling

Manual scaling lets you resize a Dedicated serving cluster when you know the target resource configuration you need. You can increase or decrease Query CU to adjust cluster capacity, or increase or decrease replicas to adjust query throughput and availability.

Manual scaling is useful for planned changes, such as production launches, load tests, migration windows, predictable traffic increases, or one-time cost optimization after traffic drops.

Note that manual scaling applies to serving clusters only. On-demand clusters scale automatically when requests arrive and scale back to zero when idle.

📘Note

Scaling Query CU manually is supported on all plans.

Scaling replicas manually is supported on the Enterprise plan and above.

Auto-scaling and scheduled scaling are supported on the Enterprise plan and above.

Before you start​

Before you start, read Plan Cluster Scaling to understand the key scaling concepts and choose the right scaling approach for your workload.

Manual scaling via web console​

Scale Query CU manually​

1

Navigate to the Cluster Details page.

2

Click on Scale in the Query CU Settings card.

3

Select Manual as the scaling method and configure the desired new query CU size.

4

Click on Save.

Scale Replica manually​

1

Navigate to the Cluster Details page.

2

Click on Scale in the Replica Settings card.

3

Select Manual as the scaling method and configure the desired new replica count.

4

Click on Save.

Manual scaling via RESTful API​

With the RESTful API, you can manually scale Query CU and replica in a single Modify Cluster request.

bash
export TOKEN="YOUR_API_KEY"
export CLUSTER_ID="inxx-xxxxxxxxxxxxxxx"

curl --request POST \
--url "${BASE_URL}/v2/clusters/${CLUSTER_ID}/modify" \
--header "Authorization: Bearer ${TOKEN}" \
--header "Accept: application/json" \
--header "Content-Type: application/json" \
-d '{
    "cuSize": 2,
    "replica": 2
}'

View scaling progress​

After a manual scaling request is submitted, Zilliz Cloud creates a job record.

1

In the Zilliz Cloud console, go to the target project.

2

Go to Jobs.

3

Find the scaling job for the target cluster.

4

Check the job status.

When the scaling job is in progress, the cluster status is Modifying. When the job succeeds, the cluster status changes back to Running.

FAQ​

When does the new configuration start billing?

The new configuration starts billing only after the scaling job completes successfully. If the job is still running or does not complete, billing remains based on the previous configuration.

What happens if scale-down is not allowed?

A scale-down request may fail if the target Query CU size cannot support the current data volume, collection count, or partition count. In this case, keep the current size or choose a larger target configuration.

Should I use manual scaling, scheduled scaling, or dynamic scaling?

Use manual scaling when you know exactly when and how much to scale. Use scheduled scaling for recurring traffic patterns. Use dynamic scaling for unpredictable workloads where Zilliz Cloud should adjust resources automatically within a configured range.

Ctrl I