Documentation

influxd inspect build-tsi

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

The influxd inspect build-tsi command rebuilds the TSI index and, if necessary, the series file.

Usage

influxd inspect build-tsi [flags]

InfluxDB builds the index by reading all Time-Structured Merge tree (TSM) indexes and Write Ahead Log (WAL) entries in the TSM and WAL data directories. If the series file directory is missing, it rebuilds the series file. If the TSI index directory already exists, the command will fail.

Adjust performance

Use the following options to adjust the performance of the indexing process:

–max-log-file-size

--max-log-file-size determines how much of an index to store in memory before compacting it into memory-mappable index files. If you find the memory requirements of your TSI index are too high, consider decreasing this setting.

–max-cache-size

--max-cache-size defines the maximum cache size. The indexing process replays WAL files into a tsm1.Cache. If the maximum cache size is too low, the indexing process will fail. Increase --max-cache-size to account for the size of your WAL files.

–batch-size

--batch-size defines the size of the batches written into the index. Altering the batch size can improve performance but may result in significantly higher memory usage.

Flags

FlagDescriptionInput Type
--batch-sizeSize of the batches to write to the index. Defaults to 10000. See above.integer
--bucket-idBucket ID (required if --shard-id is present).string
--compact-series-fileCompact existing series file. Does not rebuilt index.
--concurrencyNumber of workers to dedicate to shard index building. Defaults to GOMAXPROCS (8 by default).integer
--data-pathPath to the TSM data directory. Default is ~/.influxdbv2/engine/data.string
-h--helpHelp for the build-tsi command.
--max-cache-sizeMaximum cache size. Defaults to 1073741824. See above.uinteger
--max-log-file-sizeMaximum log file size. Defaults to 1048576. See above .integer
--shard-idShard ID (requires a --bucket-id).string
-v--verboseEnable verbose output.
--wal-pathPath to the WAL data directory. Defaults to ~/.influxdbv2/engine/wal.string

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, 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