Bug #38271 Slowdown of a replicated Master (Master-Master) with a slave each
Submitted: 21 Jul 2008 20:31 Modified: 22 Jul 2008 11:52
Reporter: Ed Zimmermann Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server: Replication Severity:S5 (Performance)
Version:5.0.51a OS:Linux (Ubuntu 6.06 LTS)
Assigned to: CPU Architecture:Any
Tags: master, replication, request, UNKNOWN

[21 Jul 2008 20:31] Ed Zimmermann 
Description:
One of our two masters in a master-master configuration replication slowed down from almost instantaneous to up to 15 minutes per query.  I optimized all I could, re-built the data from the other master that is working fine (from drop database and using a source transfer.sql) and re-granting access to users and using wireshark I am seeing many (MYSQL Request Unknown) with codes 92,64,81,82,86,74.

The people on that site are desperate!

How to repeat:
Unknown
[22 Jul 2008 9:37] Valeriy Kravchuk 
We're sorry, but the bug system is not the appropriate forum for asking help on using MySQL products. Your problem is not the result of a bug, likely.

Support on using our products is available both free in our forums at http://forums.mysql.com/ and for a reasonable fee direct from our skilled support engineers at http://www.mysql.com/support/

If you had identified repeatable, isolated test case that lead to problem like those you described, please, attach it to this report.

Thank you for your interest in MySQL.
[22 Jul 2008 11:52] Ed Zimmermann 
It does not seem to be a performance issue because why with the same queries and systems being used would one location slow down and not the other? My assistant already checked for networking problems and he found none at that location.

Would you like me to check anything else before it is considered an issue?

Thank you.
[23 Jul 2008 5:22] Valeriy Kravchuk 
I am sure you have an issue. But to call it a result of a bug in MySQL eventually one need to reproduce the problem in his own environment. So, please, add more details on how to reproduce the problem at will, that is, provide a repeatable test case.

Analysing your environment would be a kind of support activity, and bugs database is not intended for providing free support.