Comments on: MySQL Error: Client requested master to start replication from impossible position https://www.brandonchecketts.com/archives/mysql-error-client-requested-master-to-start-replication-from-impossible-position Web Programming, Linux System Administation, and Entrepreneurship in Athens Georgia Sat, 02 Sep 2023 16:41:15 +0000 hourly 1 https://wordpress.org/?v=6.9.1 By: Kevin https://www.brandonchecketts.com/archives/mysql-error-client-requested-master-to-start-replication-from-impossible-position/comment-page-1#comment-2877 Fri, 25 May 2012 20:04:44 +0000 http://www.brandonchecketts.com/?p=514#comment-2877 I’ve had to deal with these issues as well when I lost a relay server, a server that sits between the master and multiple slaves. In my case, once I had brought up the new relay server, the end slaves were at a completely different position on the old relay server. By looking at the bin logs on the slaves, I was able to find the last transaction they ran and then able to find the same transaction on the new relay server’s bin logs (once it was synced up with the master again). In this case you will most likely also need to specify a new log file in addition to the position (MASTER_LOG_FILE = ‘master_log_name’) in order to get them replicating again.

Another hint for people is to use the “show processlist” command on both the slaves and master. On the master, it shows which slaves are connected and whether it has sent all of the changes yet. On the slave, it shows what transactions it is executing as it tries to catchup with the master. Also, the “Time” column shows how many seconds behind the master it is. Once it has caught up, that column shows how long it has been in sync.

]]>