InfluxDB Enterprise startup process

On startup, InfluxDB Enterprise starts all subsystems and services in the following order:

  1. TSDBStore
  2. Monitor
  3. Cluster
  4. Precreator
  5. Snapshotter
  6. Continuous Query
  7. Announcer
  8. Retention
  9. Stats
  10. Anti-entropy
  11. HTTP API

A subsystem is a collection of related services managed together as part of a greater whole. A service is a process that provides specific functionality.

Subsystems and services


The TSDBStore subsystem starts and manages the TSM storage engine. This includes services such as the points writer (write), reads (query), and hinted handoff (HH). TSDBSTore first opens all the shards and loads write-ahead log (WAL) data into the in-memory write cache. If influxd was cleanly shutdown previously, there will not be any WAL data. It then loads a portion of each shard’s index.

Index versions and startup times

If using inmem indexing, InfluxDB loads all shard indexes into memory, which, depending on the number of series in the database, can take time. If using tsi1 indexing, InfluxDB only loads hot shard indexes (the most recent shards or shards currently being written to) into memory and stores cold shard indexes on disk. Use tsi1 indexing to see shorter startup times.


The Monitor service provides statistical and diagnostic information to InfluxDB about InfluxDB itself. This information helps with database troubleshooting and performance analysis.


The Cluster service provides implementations of InfluxDB OSS v1.8 interfaces that operate on an InfluxDB Enterprise v1.8 cluster.


The Precreator service creates shards before they are needed. This ensures necessary shards exist before new time series data arrives and that write-throughput is not affected the creation of a new shard.


The Snapshotter service routinely creates snapshots of InfluxDB Enterprise metadata.

Continuous Query

The Continuous Query (CQ) subsystem manages all InfluxDB CQs.


The Announcer service announces a data node’s status to meta nodes.


The Retention service enforces retention policies and drops data as it expires.


The Stats service monitors cluster-level statistics.


The Anti-entropy (AE) subsystem is responsible for reconciling differences between shards. For more information, see Use anti-entropy.


The InfluxDB HTTP API service provides a public facing interface to interact with InfluxDB Enterprise and internal interfaces used within the InfluxDB Enterprise cluster.

Was this page helpful?

Thank you for your feedback!

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: