By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,626 Members | 2,169 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,626 IT Pros & Developers. It's quick & easy.

Replication Master Crashed After 6 Hours

P: n/a
CK
Hello everyone,

I recently setup replication, the master and slaves appears to work
fine initially. After about 6 hours, the master mysqld process will
start to consume 99% CPU and the load (avg. load per minute) will go
to 3, 4, 6, 15, 24, 56, 312... in a matter of seconds! The master then
stops responding and needs a reboot. This problem is reproducible, I
have tested a few times.

This is a screenshot of "top" command just before the master died:
http://choonkeng.hopto.org/temp/replication-hang.gif

There are plenty of memory and no disk swapping when the master goes
99%. Error and slow logs don't show any useful information.

Can anyone shed some light?

Thanks in advanced.

Regards,
CK
Jul 20 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.