Documentation

Rebuild the TSI index

This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.

The InfluxDB Time Series Index (TSI) indexes or caches measurement and tag data to ensure queries are performant. In some cases, it may be necessary to flush and rebuild the TSI Index. Use the following steps to rebuild your InfluxDB TSI index:

1. Stop InfluxDB

Stop InfluxDB by stopping the influxd process.

2. Remove all _series directories

Remove all _series directories. By default, _series directories are stored at /data/<dbName>/_series, however you should check for and remove _series files throughout the /data directory.

3. Remove all index directories

Remove all index directories. By default, index directories are stored at /data/<dbName/<rpName>/<shardID>/index.

4. Rebuild the TSI index

Use the influx_inspect command line client (CLI) to rebuild the TSI index:

# Syntax
influx_inspect buildtsi -datadir <data_dir> -waldir <wal_dir>

# Example
influx_inspect buildtsi -datadir /data -waldir /wal

5. Restart InfluxDB

Restart InfluxDB by starting the influxd process.


Rebuild the TSI index in an InfluxDB Enterprise cluster

To rebuild the TSI index in an InfluxDB Enterprise cluster, perform the steps above on each data node in the cluster one after the other. After restarting the influxd process on a data node, allow the hinted handoff queue (HHQ) to write all missed data to the updated node before moving on to the next node.


Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.6

Key enhancements in InfluxDB 3.6 and the InfluxDB 3 Explorer 1.4.

See the Blog Post

InfluxDB 3.6 is now available for both Core and Enterprise. This release introduces the 1.4 update to InfluxDB 3 Explorer, featuring the beta launch of Ask AI, along with new capabilities for simple startup and expanded functionality in the Processing Engine.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2