Does anyone know what the expected behavior of Zabbix is when its database becomes unavailable?
That is, Zabbix 1.8.4 server with MySQL backend. MySQL dies. I know already that MySQL can be unavailable for at least an hour, and Zabbix server will pick up and start writing after it becomes available...but specifically, how does it cache? What does it cache? Are there parameters to set to deal with this more gracefully?
For example, in an environment which is using a single database (not replicated unfortunately), when the database goes down for backup (for about an hour), is it possible that Zabbix can still gather and cache that data, then write it to the database when it becomes available? Right now I have gaps during that database backup period, and I'd like to have Zabbix cache it, if possible.
Thanks,
Michael
That is, Zabbix 1.8.4 server with MySQL backend. MySQL dies. I know already that MySQL can be unavailable for at least an hour, and Zabbix server will pick up and start writing after it becomes available...but specifically, how does it cache? What does it cache? Are there parameters to set to deal with this more gracefully?
For example, in an environment which is using a single database (not replicated unfortunately), when the database goes down for backup (for about an hour), is it possible that Zabbix can still gather and cache that data, then write it to the database when it becomes available? Right now I have gaps during that database backup period, and I'd like to have Zabbix cache it, if possible.
Thanks,
Michael
Comment