[ZBXNEXT-8995] Manual Active Node Switching in Zabbix HA Configuration Created: 2024 Feb 07 Updated: 2025 May 24 |
|
| Status: | Open |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature Request | Priority: | Minor |
| Reporter: | Piotr Wegrzyn | Assignee: | Zabbix Development Team |
| Resolution: | Unresolved | Votes: | 4 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Description |
|
When running Zabbix in an HA configuration, it would be highly desirable to have functionality, ideally in the GUI, to manually change the active server. Currently, to the best of our knowledge, to failover to a specific node you must shutdown the Zabbix Server on all the other nodes and wait for it to hit the configured failover time limit. There’s a variety of scenarios where it’s desirable to manually change the active node without delay. |
| Comments |
| Comment by jchegedus [ 2024 Apr 08 ] |
|
Building up on this, not only manually set the the active is useful as having a weight rule or preferable active node(s). According to the documentation we have possibly: may have several modes: active, standby, unavailable, stopped Along with those states would be reasonable and possibly feasible to implement preference rules as well, notwithstanding the possible modes set on configuration, manually, it also should be an option to use the `-R` function from the binary to set the status of a cluster member. |