Documentation

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

TSDBStore

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.

Monitor

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

Cluster

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

Precreator

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.

Snapshotter

The Snapshotter service routinely creates snapshots of InfluxDB Enterprise metadata.

Continuous Query

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

Announcer

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

Retention

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

Stats

The Stats service monitors cluster-level statistics.

Anti-entropy

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

HTTP API

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!


Set your InfluxDB URL

Linux Package Signing Key Rotation

All signed InfluxData Linux packages have been resigned with an updated key. If using Linux, you may need to update your package configuration to continue to download and verify InfluxData software packages.

For more information, see the Linux Package Signing Key Rotation blog post.

InfluxDB Cloud backed by InfluxDB IOx

All InfluxDB Cloud organizations created on or after January 31, 2023 are backed by the new InfluxDB IOx storage engine. Check the right column of your InfluxDB Cloud organization homepage to see which InfluxDB storage engine you’re using.

If powered by IOx, this is the correct documentation.

If powered by TSM, see the TSM-based InfluxDB Cloud documentation.

InfluxDB Cloud backed by InfluxDB TSM

All InfluxDB Cloud organizations created on or after January 31, 2023 are backed by the new InfluxDB IOx storage engine which enables nearly unlimited series cardinality and SQL query support. Check the right column of your InfluxDB Cloud organization homepage to see which InfluxDB storage engine you’re using.

If powered by TSM, this is the correct documentation.

If powered by IOx, see the IOx-based InfluxDB Cloud documentation.

State of the InfluxDB Cloud (IOx) documentation

The new documentation for InfluxDB Cloud backed by InfluxDB IOx is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.