# Reindexing on Vespa Cloud

[](/en/operations/reindexing-cloud.html.md "View as Markdown") 

When the indexing pipeline of an application changes, Vespa may need to [reindex](reindexing.html) stored data so the index reflects the new specification. On Vespa Cloud this is handled for you: reindexing is enabled and started automatically as part of your deployment, and you can follow, pause, resume, re-trigger, and tune it from the [Vespa Cloud console](https://console.vespa-cloud.com/). There is no need to call the [reindex](../reference/api/deploy-v2.html#reindex) endpoint and redeploy manually as you would in a [self-managed](self-managed/admin-procedures.html) deployment.

This page describes the Vespa Cloud workflow. See [Reindexing](reindexing.html) for the underlying concepts, reindexing states, and schema-change use cases that apply to all deployments.

## How reindexing is triggered

When you deploy a change that requires reindexing (see [changes that require reindexing](../reference/schemas/schemas.html#changes-that-require-reindexing) for the full list), Vespa Cloud enables and starts reindexing automatically once the deployment has converged on the new configuration. This replaces the manual procedure in a self-managed deployment, where reindexing is enabled through the [reindex endpoint](../reference/api/deploy-v2.html#reindex) and started with another redeployment.

Only the stored [document fields](../reference/schemas/schemas.html#document) are re-fed; all derived fields are recomputed. Reindexing runs in the background, but how much it affects the cluster depends on the available resources and the current load. You control this trade-off with the [reindexing speed](#controlling-reindexing): a lower speed uses fewer resources and has less impact on concurrent feed and queries, while a higher speed completes sooner at the cost of higher load. Until reindexing completes, affected fields may be empty or carry annotations that do not match the new configuration.

## Controlling reindexing from the console

Reindexing is managed per content cluster from the **Clusters** view of a deployment in the [Vespa Cloud console](https://console.vespa-cloud.com/). Each content cluster lists its document types with the current reindexing _state_, _speed_, _progress_, and start and end times.

 ![Reindexing table and controls for a content cluster in the Vespa Cloud console](/assets/img/console/reindex-overview.png)

Select one or more document types to:

- **Reindex**: trigger a fresh reindexing, for example after deploying a [document processor](../applications/document-processors.html) that transforms data, or to re-run an earlier reindexing.
- **Pause** and **Resume**: temporarily halt an ongoing reindexing, and resume it later from where it stopped.
- **Disable reindexing**: stop reindexing for the selected document types.

When you trigger reindexing, a dialog lets you choose the **reindexing speed**: _Conservative_, _Balanced_ (the recommended default), or _Aggressive_. The speed balances time to completion against resource usage: a more aggressive speed completes reindexing sooner but consumes more of the cluster's resources, while a more conservative speed reduces the impact on concurrent feed and queries.

 ![Dialog for confirming reindexing and selecting the reindexing speed](/assets/img/console/reindex-confirm.png)
## Monitoring progress

The Clusters view shows live progress for each document type: the _state_ (_pending_, _running_, _successful_, or _failed_), a completion percentage, and the start and end times.

 ![A completed reindexing showing state successful and 100% progress](/assets/img/console/reindex-completed.png)

In addition, a running reindexing is shown as a _Reindexing_ annotation on the metric charts. See [Monitoring](monitoring.html) for details. This makes it easy to correlate reindexing with any change in feed or query latency while it runs.

## Related

- [Reindexing](reindexing.html): concepts, states, and schema-change use cases
- [Changes that require reindexing](../reference/schemas/schemas.html#changes-that-require-reindexing)
- [Monitoring](monitoring.html): annotations and metrics
- [Reindexing API reference](../reference/api/deploy-v2.html#reindexing)

 Copyright © 2026 - [Cookie Preferences](#)