Cluster Node Configuration

Warning! This page documents an old version of InfluxDB, which is no longer actively developed. InfluxDB v1.3 is the most recent stable version of InfluxDB.

Note: Clustering is now a commerial product called InfluxEnterprise. More information can be found here.

The following sections describe the different node types in an InfluxDB cluster and show how to configure them.

General node configuration

Each node’s configuration file must specify:

  • A bind-address in the [meta] section. This is the address for cluster wide communication.
  • An http-bind-address in the [meta] section. This is the address for consensus service communication.
  • A bind-address in the [http] section. This is the address for the HTTP API.

Each configuration option should indicate the node’s IP address or hostname followed by the port (see the next sections for examples).

NOTE: The hostnames for each machine must be resolvable by all members of the cluster.

Consensus node

Consensus nodes run only the consensus service. The consensus service ensures consistency across the cluster for node membership, databases, retention policies, users, continuous queries, shard metadata, and subscriptions.

Configuration:

[meta]
  enabled = true #✨
  ...
  bind-address = "<IP>:8088"
  http-bind-address = "<IP>:8091"

...

[data]
  enabled = false #✨

[http]
  ...
  bind-address = "<IP>:8086"

Data node

Data nodes run only the data service. The data service stores the actual time series data and responds to queries about those data.

Configuration:

[meta]
  enabled = false #✨
  ...
  bind-address = "<IP>:8088"
  http-bind-address = "<IP>:8091"

...

[data]
  enabled = true #✨

[http]
  ...
  bind-address = "<IP>:8086"

Hybrid node

Hybrid nodes run both the consensus and data services.

Configuration:

[meta]
  enabled = true #✨
  ...
  bind-address = "<IP>:8088"
  http-bind-address = "<IP>:8091"

...

[data]
  enabled = true #✨

[http]
  ...
  bind-address = "<IP>:8086"