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

Use correct binlog position in mm_mysqlmon

Browse Source 
Position 310 is not guaranteed to always exist on the master if the binlog
is just created. Position 4 will always be a valid position.
This commit is contained in:
Markus Mäkelä
2017-10-02 11:22:13 +03:00
parent 6a33e55b6f
commit 4f675997fb
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
maxscale-system-test/mm_mysqlmon.cpp
View File

@ -84,7 +84,7 @@ void check_group(TestConnections *Test, const char *server, const char *group)
void change_master(TestConnections *Test, int slave, int master) void change_master(TestConnections *Test, int slave, int master)
{ {
execute_query(Test->repl->nodes[slave], "CHANGE MASTER TO master_host='%s', master_port=3306, " execute_query(Test->repl->nodes[slave], "CHANGE MASTER TO master_host='%s', master_port=3306, "
"master_log_file='mar-bin.000001', master_log_pos=310, master_user='repl', master_password='repl';START SLAVE", "master_log_file='mar-bin.000001', master_log_pos=4, master_user='repl', master_password='repl';START SLAVE",
Test->repl->IP[master], Test->repl->user_name, Test->repl->password); Test->repl->IP[master], Test->repl->user_name, Test->repl->password);
} }