TSDB for InfluxDB® offers two instance editions: Basic Edition and High-availability Edition. The High-availability Edition uses a three-node architecture based on the Raft consensus protocol and applies to more than 80% of user scenarios.
Use cases
The High-availability Edition is suited for workloads that require continuous data availability and consistency:
Monitoring basic Internet resources and containers
Monitoring industrial production security
Monitoring and analyzing business operations
Remotely monitoring IoT (Internet of Things) devices in real time
Assessing production quality
Backtracking faults
How it works
The High-availability Edition runs three database nodes: one primary node and two secondary nodes. All three nodes are deployed in the same zone.
Node roles:
| Node | Role | Description |
|---|---|---|
| Primary node | Write handler | Accepts write requests and replicates data logs to both secondary nodes. |
| Secondary nodes (x2) | Standby replicas | Receive replicated data logs from the primary node. |
Write confirmation: A write succeeds only after data is persisted on at least two of the three nodes. This quorum-based approach means a single node failure does not cause data loss.
Data consistency: The Raft consensus protocol synchronizes data changes among all nodes to ensure linear consistency.
Limitations
All three nodes of a High-availability Edition instance are deployed in the same zone to ensure high performance.
FAQ
Can I upgrade a Basic Edition instance to a High-availability Edition instance?
No. Upgrading from Basic Edition to High-availability Edition is not supported.