Esa Korhonen 3ec449339f Only write to SERVER->status at the end of a monitoring loop ...

This makes the code clearer and reduces race conditions, as the monitor
could be writing SERVER->status while a router is reading it. Also,
the time during which the SERVER struct is locked drops to a fraction.

2018-05-23 16:19:08 +03:00

..

cluster_discovery.cc

Only write to SERVER->status at the end of a monitoring loop

2018-05-23 16:19:08 +03:00

cluster_manipulation.cc

Only write to SERVER->status at the end of a monitoring loop

2018-05-23 16:19:08 +03:00

CMakeLists.txt

MXS-1703 Use a common header for all mariadbmon files

2018-04-12 13:06:36 +03:00

gtid.cc

MXS-1703 Run astyle, rewrite comments & reorder fields

2018-04-13 13:33:13 +03:00

gtid.hh

MXS-1703 Use a common header for all mariadbmon files

2018-04-12 13:06:36 +03:00

mariadbmon_common.cc

MXS-1845 Cleanup monitor backend updating

2018-05-18 13:48:08 +03:00

mariadbmon_common.hh

MXS-1845 Cleanup monitor backend updating

2018-05-18 13:48:08 +03:00

mariadbmon.cc

Only write to SERVER->status at the end of a monitoring loop

2018-05-23 16:19:08 +03:00

mariadbmon.hh

Only write to SERVER->status at the end of a monitoring loop

2018-05-23 16:19:08 +03:00

mariadbserver.cc

Only write to SERVER->status at the end of a monitoring loop

2018-05-23 16:19:08 +03:00

mariadbserver.hh

Only write to SERVER->status at the end of a monitoring loop

2018-05-23 16:19:08 +03:00