Documentation

Rebuild the TSI index

In some cases, it may be necessary to flush and rebuild the TSI index. For example, purging corrupt index files or removing outdated indexed data.

To rebuild your InfluxDB TSI index:

  1. Stop the InfluxDB (influxd) process.

    Rebuilding the TSI index while the influxd is running could prevent some data from being queryable.

  2. Navigate to the data directory in your InfluxDB engine path. The engine path depends on your operating system or custom engine path setting.

    cd ~/.influxdbv2/engine/data/
    
    cd -Path 'C:\%USERPROFILE%\.influxdbv2\engine\data\'
    
  3. Delete all _series directories in your InfluxDB data directory. By default, _series directories are are stored at /data/<bucket-id>/_series, but check for and remove _series directories throughout the data directory.

    find . -type d -name _series -exec -delete
    
    get-childitem -Include _series -Recurse -force | Remove-Item -Force -Recurse
    
  4. Delete all index directories. By default, index directories are stored at /data/<bucket-id>/autogen/<shard-id>/index, but check for and remove index directories throughout the data directory.

    find . -type d -name index -exec -delete
    
    get-childitem -Include index -Recurse -force | Remove-Item -Force -Recurse
    
  5. Use the influxd inspect build-tsi command to rebuild the TSI index.

    influxd inspect build-tsi
    

Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: