Skip to content

High Availability

CrateDB offers a shared-nothing architecture to run highly available clusters, ensuring excellent performance with zero downtime at a minimal operational effort. In contrast to a primary-secondary architecture, every node can perform every operation and all nodes are configured in the same way. CrateDB keeps running – even in case of hardware failures, network issues, or maintenance tasks. If needed, CrateDB can easily be deployed across availability zones or data centers. CrateDB natively provides automatic replication of data to a configurable number of nodes in the cluster. The ability to execute rolling software upgrades ensures no interruption of data access during maintenance operations. In addition, CrateDB clusters are self-healing, i.e., nodes that re-join a cluster after a failover automatically synchronize with the latest data.

Securing high availability in a shared-nothing architecture


1. The failed node leaves the cluster due to some hardware failure or a rolling upgrade.


3. CrateDB performs an automatic failover, where all the data remain available on the other nodes. 


3. As the new node joins, automatic data synchronization and rebalancing take place.   


4. Once the new node is part of the system and data are fully replicated again, the self-healing process is completed.

Product documentation



Additional resources

CrateDB at Big Data Conference Europe 2022

Not all Time-Series are Equal – Challenges of Storing and Analyzing Industrial Data.

Timestamp: 12:22 – 18:53