From 51e6166423db94f173248dc42c46825529a18900 Mon Sep 17 00:00:00 2001 From: MassimilianoPinto Date: Thu, 3 Sep 2015 13:54:28 +0200 Subject: [PATCH] Added RESET SLAVE Added RESET SLAVE --- .../Replication-Proxy-Binlog-Router-Tutorial.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/Documentation/Tutorials/Replication-Proxy-Binlog-Router-Tutorial.md b/Documentation/Tutorials/Replication-Proxy-Binlog-Router-Tutorial.md index f6bc6dd5c..9c756b8a0 100644 --- a/Documentation/Tutorials/Replication-Proxy-Binlog-Router-Tutorial.md +++ b/Documentation/Tutorials/Replication-Proxy-Binlog-Router-Tutorial.md @@ -314,14 +314,22 @@ The above scenario might refer to a master crash/failure: Truncating the previous MaxScale binlog is safe as that incomplete transaction is lost. It should be checked that current master or new one has the new bnlog file, in case of any error replication stops and errors are reported via SHOW SLAVE STATUS and in error logs. - MySQL> START SLAVE; + MariaDB> START SLAVE; Check for any error in log files and with - MySQL> SHOW SLAVE STATUS; + MariaDB> SHOW SLAVE STATUS; In some situations replication state could be STOPPED and proper messages are displyed in error logs and in SHOW SLAVE STATUS +In order to resolve any mistake done with CHANGE MASTER TO MASTER_LOG_FILE / MASTER_LOG_POS, another administrative command would be helpful. + + MariaDB> RESET SLAVE; + +This command removes master.ini file, blanks all master configuration in memory and sets binlog router in unconfigured state: a CHANHE MASTER TO command should be issued for the new configuration. + +Note: existing binlog files are not touched by this command. + ### Slave servers setup Examples of CHANGE MASTER TO command issued on a slave server that wants to gets replication events from MaxScale binlog router: