Set up multi-node on self-hosted TimescaleDB

URL: llms-txt#set-up-multi-node-on-self-hosted-timescaledb

Contents:

• Set up multi-node on self-hosted TimescaleDB
  • Setting up multi-node on self-hosted TimescaleDB

[Multi-node support is sunsetted][multi-node-deprecation].

TimescaleDB v2.13 is the last release that includes multi-node support for Postgres versions 13, 14, and 15.

To set up multi-node on a self-hosted TimescaleDB instance, you need:

• A Postgres instance to act as an access node (AN)
• One or more Postgres instances to act as data nodes (DN)
• TimescaleDB [installed][install] and [set up][setup] on all nodes
• Access to a superuser role, such as postgres, on all nodes

The access and data nodes must begin as individual TimescaleDB instances. They should be hosts with a running Postgres server and a loaded TimescaleDB extension. For more information about installing self-hosted TimescaleDB instances, see the [installation instructions][install]. Additionally, you can configure [high availability with multi-node][multi-node-ha] to increase redundancy and resilience.

The multi-node TimescaleDB architecture consists of an access node (AN) which stores metadata for the distributed hypertable and performs query planning across the cluster, and a set of data nodes (DNs) which store subsets of the distributed hypertable dataset and execute queries locally. For more information about the multi-node architecture, see [about multi-node][about-multi-node].

If you intend to use continuous aggregates in your multi-node environment, check the additional considerations in the [continuous aggregates][caggs] section.