mirror of https://github.com/apache/druid.git
2.2 KiB
2.2 KiB
| layout | title |
|---|---|
| doc_page | High Availability |
High Availability
ZooKeeper, metadata store, the coordinator, the overlord, and brokers are recommended to set up a high availability environment.
- For highly-available ZooKeeper, you will need a cluster of 3 or 5 ZooKeeper nodes. We recommend either installing ZooKeeper on its own hardware, or running 3 or 5 Master servers (where overlords or coordinators are running) and configuring ZooKeeper on them appropriately. See the ZooKeeper admin guide for more details.
- For highly-available metadata storage, we recommend MySQL or PostgreSQL with replication and failover enabled. See MySQL HA/Scalability Guide and PostgreSQL's High Availability, Load Balancing, and Replication for MySQL and PostgreSQL, respectively.
- For highly-available Druid Coordinators and Overlords, we recommend to run multiple servers. If they are all configured to use the same ZooKeeper cluster and metadata storage, then they will automatically failover between each other as necessary. Only one will be active at a time, but inactive servers will redirect to the currently active server.
- Druid Brokers can be scaled out and all running servers will be active and queryable. We recommend placing them behind a load balancer.