Zabbix built-in HA Vs Pacemaker/corosync
Built-in HA in Zabbix
Since Zabbix 7.0, Zabbix Server has built-in high availability (HA) support. This means:
- You can run multiple Zabbix server nodes.
- Only one is active at a time.
- The others are standby and can take over if the active one fails.
- Failover is handled internally by Zabbix, using database coordination (it stores node status in the DB).
So why Pacemaker and Corosync then?
You don’t need Pacemaker + Corosync for the Zabbix Server itself anymore if you’re using built-in HA.
However, there are still scenarios where Pacemaker/Corosync may be useful:
When to Use Pacemaker/Corosync
- Database Failover:
- Zabbix’s built-in HA does not handle database HA.
- Pacemaker/Corosync can manage MySQL/MariaDB/PostgreSQL clusters with automatic failover.
2. Frontend High Availability:
- Zabbix frontend (Apache/Nginx + PHP) does not have built-in HA.
- You can use Pacemaker/Corosync (or HAProxy/Keepalived) to manage failover of frontend nodes and virtual IPs.
3. Virtual IP Management:
- Built-in HA in Zabbix does not provide a virtual IP.
Tools like Pacemaker or Keepalived are needed if you want a static virtual IP for the Zabbix server that always points to the active node.
Comments
Post a Comment