Documentation

Glossary

data node

A node that runs the data service.

For high availability, installations must have at least two data nodes. The number of data nodes in your cluster must be the same as your highest replication factor. Any replication factor greater than two gives you additional fault tolerance and query capacity within the cluster.

Data node sizes will depend on your needs. The Amazon EC2 m4.large or m4.xlarge are good starting points.

Related entries: data service, replication factor

data service

Stores all time series data and handles all writes and queries.

Related entries: data node

meta node

A node that runs the meta service.

For high availability, installations must have three meta nodes. Meta nodes can be very modestly sized instances like an EC2 t2.micro or even a nano. For additional fault tolerance installations may use five meta nodes; the number of meta nodes must be an odd number.

Related entries: meta service

meta service

The consistent data store that keeps state about the cluster, including which servers, databases, users, continuous queries, retention policies, subscriptions, and blocks of time exist.

Related entries: meta node

replication factor

The attribute of the retention policy that determines how many copies of the data are stored in the cluster. InfluxDB replicates data across N data nodes, where N is the replication factor.

To maintain data availability for queries, the replication factor should be less than or equal to the number of data nodes in the cluster:

  • Data is fully available when the replication factor is greater than the number of unavailable data nodes.
  • Data may be unavailable when the replication factor is less than the number of unavailable data nodes.

Any replication factor greater than two gives you additional fault tolerance and query capacity within the cluster.

web console

Legacy user interface for the InfluxDB Enterprise.

This has been deprecated and the suggestion is to use Chronograf.

If you are transitioning from the Enterprise Web Console to Chronograf, see how to transition from the InfluxDB Web Admin Interface.


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.