Install EDR
EDR ships as pre-built binaries. You don’t build anything from source.
Binaries
| Binary | What it is |
|---|---|
influxdb3 | InfluxDB 3 Enterprise server (built and shipped by InfluxData). |
influxdb3-edr | The EDR agent. Runs one process per node that participates in replication. |
edr-inspect | Read-only triage CLI (state, metrics, and topology). See Monitor EDR. |
Place the binaries on each host—on PATH, or referenced by an absolute
path in your service definitions. EDR has no other runtime dependencies.
EDR version support
EDR 1.0.0 supports InfluxDB 3 Enterprise 3.11.x and 3.12.x. InfluxDB 3 Enterprise 3.10.x is unvalidated and unsupported for GA. See Compatibility for the supported storage-format matrix.
Requirements
The influxdb3 server must run the
upgraded storage engine—the
default for new clusters on 3.11+.
For an existing 3.10 deployment, follow the
staged upgrade before installing EDR 1.0.0. EDR reads the upgraded engine’s object store
directly, so without it,
write-ahead log (WAL)
files are in a format EDR ignores.
Run one influxdb3-edr agent per node that sources or receives data. Each
agent needs a token store directory and a config file—see
Configure EDR.
Confirm your version
influxdb3 --version
influxdb3-edr --versionConfigure EDR
Every influxdb3-edr agent needs a config file, a token store, and the
following CLI flags:
influxdb3-edr \
--config /etc/edr/config.yaml \
--data-dir /var/lib/influxdb3 \
--token-store /etc/edr/secrets \
--state-location /var/lib/edr/state \
--listen 0.0.0.0:9090| Flag | Description |
|---|---|
--data-dir | InfluxDB data directory (the shared object store). |
--token-store | Path to the token store directory. See Manage tokens. |
--state-location | Where the agent persists replication state. See State and recovery. |
--listen | Network listener for the replication protocol. Defaults to 0.0.0.0:9090. |
For the replication topology config (downstream: and upstreams:), see
Get started. For the complete CLI flag
reference, see CLI reference. For the
complete config file schema, see
Configuration file reference.
Run EDR in Docker
The agent and edr-inspect also ship as a container image. For
operating that image—ports, mounts, the environment contract, and triage
through docker exec—see Run EDR in Docker.
Run EDR on Kubernetes
Use the supported Helm chart to deploy a sender, receiver, or combined relay alongside an existing Enterprise release. See Install EDR on Kubernetes.
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB 3 Enterprise and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support. Customers using a trial license can email trial@influxdata.com for assistance.