Follow

Keep Up to Date with the Most Important News

By pressing the Subscribe button, you confirm that you have read and are agreeing to our Privacy Policy and Terms of Use
Contact

Why MySQL slave stops syncing with error 1449?

I have implemented a replica from a MySQL database. The issue is, after 2 days, the slave doesn’t get sync anymore and it throws:

Coordinator stopped because there were error(s) in the worker(s). The most recent failure being: Worker 1 failed executing transaction ‘ANONYMOUS’ at source log mysql-bin.000004, end_log_pos 4321483. See error log and/or performance_schema.replication_applier_status_by_worker table for more details about this failure or others, if any.

Also, the Last_SQL_Errno is 1449. Any idea what’s the issue and how can I make it working/syncing with master again?

MEDevel.com: Open-source for Healthcare and Education

Collecting and validating open-source software for healthcare, education, enterprise, development, medical imaging, medical records, and digital pathology.

Visit Medevel

enter image description here

>Solution :

Error 1449 means, that a user which exists on source, doesn’t exist on replica, and therefore replica cannot execute the statement. Most likely this is a a CREATE (view/trigger/procedure) with a definer which doesn’t exist on the replica.

You can check the command and user by using the mysqlbinlog tool on the replica machine:

mysqlbinlog --read-from-remote-server --host=source_server -uusername mysql-bin.000004 --j 4321483

Add a comment

Leave a Reply

Keep Up to Date with the Most Important News

By pressing the Subscribe button, you confirm that you have read and are agreeing to our Privacy Policy and Terms of Use

Discover more from Dev solutions

Subscribe now to keep reading and get access to the full archive.

Continue reading