Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Current »

Check replication process is running on master and slave
Command 
show processlist;
If replication process is running, check if slave is lagging behind master.
Command to start 
 start master


If replication process is running, check if slave is lagging behind master.
Check the status 
show master status \g; show slave status \g;

Looking at output from above commands, you'd know

  • if slave is lagging behind master.
  • replication is failing because of some issues replicating a sql on slave.


If replication process has stopped due to duplicate entry in the slave.
Solution 
STOP SLAVE;
SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; /*This is to skip the duplicate record*/
START SLAVE;

References

http://www.redips.net/mysql/replication-slave-relay-log-corrupted/

http://dba.stackexchange.com/questions/53893/mysql-relay-log-corrupted-how-do-i-fix-it-tried-but-failed

https://www.percona.com/blog/2014/10/08/mysql-replication-got-fatal-error-1236-causes-and-cures/




  • No labels

The Bahmni documentation is licensed under Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)