Track the number of performed monitoring intervals

Tracking how many times the monitor has performed its monitoring allows
the test framework to consistently wait for an event instead of waiting
for a hard-coded time period. The MaxCtrl `api get` command can be used to
easily extract the numeric value.
This commit is contained in:
Markus Mäkelä
2018-06-05 14:03:38 +03:00
parent cfe676b1c8
commit f2b2951c99
10 changed files with 12 additions and 0 deletions

View File

@ -123,6 +123,7 @@ monitorMain(void *arg)
while (!handle->shutdown)
{
atomic_add_uint64(&monitor->ticks, 1);
lock_monitor_servers(monitor);
servers_status_pending_to_current(monitor);

View File

@ -545,6 +545,7 @@ monitorMain(void *arg)
/* reset cluster members counter */
is_cluster = 0;
atomic_add_uint64(&mon->ticks, 1);
lock_monitor_servers(mon);
servers_status_pending_to_current(mon);

View File

@ -270,6 +270,7 @@ void GRMon::main()
while (!m_shutdown)
{
atomic_add_uint64(&m_monitor->ticks, 1);
lock_monitor_servers(m_monitor);
servers_status_pending_to_current(m_monitor);

View File

@ -2204,6 +2204,7 @@ monitorMain(void *arg)
/* reset num_servers */
num_servers = 0;
atomic_add_uint64(&mon->ticks, 1);
lock_monitor_servers(mon);
servers_status_pending_to_current(mon);

View File

@ -543,6 +543,7 @@ monitorMain(void *arg)
}
nrounds += 1;
atomic_add_uint64(&mon->ticks, 1);
lock_monitor_servers(mon);
servers_status_pending_to_current(mon);

View File

@ -347,6 +347,7 @@ monitorMain(void *arg)
}
nrounds += 1;
atomic_add_uint64(&mon->ticks, 1);
lock_monitor_servers(mon);
servers_status_pending_to_current(mon);