hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

MXS-3800: Explain lost_slave events

Browse Source 
Currently the state change explanations are only added to mariadbmon. They
are less relevant for Galera clusters as they themselves explain why they
change their states but should still be added to make them easier to
analyze.

The event that isn't explained and is most often encountered is the loss
of a Slave status. Most often the loss of a Slave status happens because
either the IO thread or the SQL thread has stopped. Printing the states of
the threads as well as the latest error should hint at what caused the
outage.

The information can be added to the REST API in 2.5 where the monitors can
add extra information to the server JSON.
This commit is contained in:
Markus Mäkelä
2021-10-18 08:59:14 +03:00
parent 136d0271df
commit 0bf5641d80
8 changed files with 84 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
server/modules/monitor/mariadbmon/mariadbmon.hh
View File

@ -107,9 +107,10 @@ public:
bool run_manual_reset_replication(SERVER* master_server, json_t** error_out);
protected:
void pre_loop() override;
void tick() override;
void process_state_changes() override;
void pre_loop() override;
void tick() override;
void process_state_changes() override;
std::string annotate_state_change(mxs::MonitorServer* server) override final;
private:
// Some methods need a log on/off setting.