Accidentally ran CHANGE MASTER TO on master

In setting up a second mysql instance, I accidentally pasted the CHANGE MASTER TO command intended for the slave instance onto the msater instance instead. I’ve since run STOP SLAVE and RESET MASTER on the master and while SHOW MASTER STATUS now looks correct, it also gives output when I run SHOW SLAVE STATUS, e.g.

mysql> show master status;±-----------------±---------±-------------±-----------------+| File | Position | Binlog_Do_DB | Binlog_Ignore_DB |±-----------------±---------±-------------±-----------------+| mysql-bin.000001 | 107 | | |±-----------------±---------±-------------±-----------------+1 row in set (0.00 sec)mysql> show slave status\G*************************** 1. row *************************** Slave_IO_State: Master_Host: [IP REDACTED] Master_User: replicator Master_Port: 3306 Connect_Retry: 60 Master_Log_File: Read_Master_Log_Pos: 4 Relay_Log_File: mysqld2-relay-bin.000001 Relay_Log_Pos: 4 Relay_Master_Log_File: Slave_IO_Running: No Slave_SQL_Running: No

I don’t see a file, so I’m not sure why it still have slave status info. Is there a way to fix this or will it cause any problems?

When you ran “reset master” on your master, it reset the master binary logs and index file, not the new slave config you accidently setup by running the “change master to” statement. You’ll need to run “reset slave” on the master to remove the slave configuration (however you will still see the slave information when running “show slave status” on the master until the master is reset; after that, running “show slave status” should return nothing).

I had done a RESET SLAVE followed by RESET MASTER but I still see output from SHOW SLAVE STATUS. I now have replication properly working between this master and its slave despite the output I get from SHOW SLAVE STATUS. If that won’t cause problems, I assume it’s fine to leave it as is.