MySQL Bugs: #10502: Stress: Intermittent server crashes during stress

Bug #10502	Stress: Intermittent server crashes during stress
Submitted:	10 May 2005 11:21	Modified:	23 Oct 2005 10:16
Reporter:	Disha	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.0.4 Beta	OS:	Linux (Linux)
Assigned to:		CPU Architecture:	Any

Description:
The server crashes during stress with multple clients acessing the same databases at a time.

Find attached the following logs for analysis:
1) Master-Status_log-20050509_old2.log : This log file is generated by the server monitor tool that checks server status every 10 secs and restarts if required.
2) Mysql500_old2.log
3) mysql-error2.err

How to repeat:
1) Create multiple clients and hit the server using the clients with various DML and DDL statements.

Server loses connection during stress

Attachment: Stress_LostConn.rar (application/octet-stream, text), 178.73 KiB.

Hi Disha,

Thank you for your bug report!

We do need a repeatable test case to proceed with this bug.  The one that you provided:
Create multiple clients and hit the server using the clients with various DML
and DDL statements.

This is not sufficient for me to repeat the problem.  Have you since noticed a
particular query that crashed the server?  If so could you provide the query
and the table structure?

Best Regards

Hi Mathew,

The scripts/queries when run individually does not cause a server crash. I believe the issue is when we have multiple clients hitting the server simultaneously.

Please find test scripts at the following location
Globally : ftp://in.dishatech.com
Username: mysql
Password: EF4Nt3e2

Browse to Folder /Delivery/Functional_tests.

thanks.

Hi Disha,

Is everything in the Functional_Tests dir needed?  If so can you create a .tar.gz file of all
the contents for me?  It's much easier and quicker this way.

Thanks!

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".