Bug #27578 The clients connect to MySQL versy slow
Submitted: 2 Apr 2007 3:03 Modified: 2 May 2007 3:58
Reporter: tian tian Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S5 (Performance)
Version:4.1.10NT OS:Windows (Windows advance server 2000)
Assigned to: CPU Architecture:Any
Tags: error, hang out, query, replicate, slow

[2 Apr 2007 3:03] tian tian
Description:
Please help me.
I have 2 server running Windows 2000 advance server OS and 10 client. One of server is Primary server (named Svr1), other one is Backup Server (named Svr2).
My clients using a software which coding by Java (named BDS). This software will connect to MySQL Server on Svr1.
Now, I have a problem. That is, I setup replication between Svr1 and Svr2. When I configured sucessfully, replication run OK, my BDS on 10 clients still can connect to MySQL server on Svr1 but the BDS run very very slow.
I guess the cause of this problem is replication between Svr1 and Svr2, so I disable this replication process, this time, the BDS run normally.
I tried to check my.ini, mySQL's system variables, check grants privilege for accounts in MySQL, compare the values when replicate and non-replicate but I can't find cause of this problem.
I don't known why having this problem...Who known or can guess the cause of thing, please tell me. Thanks in advance.

How to repeat:
I think it's difficult to simulate this probblem because I don't know why that. You can do following steps which I descripted above. I hope you'll get similar in this problem.
[2 Apr 2007 3:58] Valeriy Kravchuk
Thank you for a problem report. Please, try to repeat with a newer version, 4.1.22, on both master and slave. In case of the same problem, please, send my.ini files from Srv1 and Srv2, and describe the hardware used.
[2 May 2007 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".