Timeline for MySQL replication problem: slave has become out of sync
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 22, 2011 at 20:40 | comment | added | Dave Rix | I wouldn't go for the crude option, as only taking some of the tables may screw up the integrity with other tables... You may be better to use something like Xtrabackup from Percona, which will allow you to do a live backup of the master, including the log positions. You can then restore the backup to the slave, set the replication positions appropriately and away you go. I think what I'm trying to say, is ditch the slave and re-create it to be safe! That is assuming you can afford to loose the slave for the duration! (but having said that, it's currently useless!) | |
| Nov 22, 2011 at 14:49 | comment | added | artfulrobot | Crude solution: should I stop the master (rather not!); stop the slave; copy the affected tables from master to slave; restart master; restart slave? | |
| Nov 22, 2011 at 14:30 | comment | added | artfulrobot | Thanks @DaveRix I like the idea of finding a shared point in history (i.e. backup) and resetting master log to reply from that place. But not sure how I'd identify that point on the master? | |
| Nov 22, 2011 at 12:02 | history | answered | Dave Rix | CC BY-SA 3.0 |