I'm running two MySQL 5.0.92 machines configured for master-master replication. Both use MyISAM. One is hosted on SingleHop, one is on an Amazon EC2 instance.
I've been running this configuration for several months with no major issues. For the last week, though, I've had a few occurrences of duplicate key errors causing replication to break (mostly due to entering invalid manual updates). When this happens my usual approach is to switch all programs to use the SingleHop instance, "stop slave" on the Amazon instance, then investigate the cause. The last couple times I've done this "stop slave" has sat spinning for a long time (I once let it sit for a couple hours and it never completed) and I've ended up just killing MySQL, resyncing the data, and restarting.
Does anyone have any idea what would cause "stop slave" to run so long without completing?
I've been running this configuration for several months with no major issues. For the last week, though, I've had a few occurrences of duplicate key errors causing replication to break (mostly due to entering invalid manual updates). When this happens my usual approach is to switch all programs to use the SingleHop instance, "stop slave" on the Amazon instance, then investigate the cause. The last couple times I've done this "stop slave" has sat spinning for a long time (I once let it sit for a couple hours and it never completed) and I've ended up just killing MySQL, resyncing the data, and restarting.
Does anyone have any idea what would cause "stop slave" to run so long without completing?