From 0750e93eeb9cd06536af0cc43c68be0c2539fd64 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Markus=20M=C3=A4kel=C3=A4?= Date: Thu, 12 Jul 2018 23:21:22 +0300 Subject: [PATCH] Fix verify_master_failure The master failure verification would not work if the slaves did not have a state change since MaxScale had started. This can be fixed by treating the startup of MaxScale as an event of sorts. --- server/modules/monitor/mariadbmon/mariadbserver.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/server/modules/monitor/mariadbmon/mariadbserver.cc b/server/modules/monitor/mariadbmon/mariadbserver.cc index c8397ed9b..135217dfa 100644 --- a/server/modules/monitor/mariadbmon/mariadbserver.cc +++ b/server/modules/monitor/mariadbmon/mariadbserver.cc @@ -47,7 +47,7 @@ MariaDBServer::MariaDBServer(MXS_MONITORED_SERVER* monitored_server, int config_ , m_n_slaves_running(0) , m_n_slave_heartbeats(0) , m_heartbeat_period(0) - , m_latest_event(0) + , m_latest_event(time(NULL)) , m_gtid_domain_id(GTID_DOMAIN_UNKNOWN) , m_topology_changed(true) , m_print_update_errormsg(true)