Over the past week a user from linux1 kept crashing mysql1 at odd times throughout the day. We traced it to 1 user specifically and found the database eating up the full /tmp partitian with one of their query sorts. So we created a larger 10Gig folder for /tmp and move mysql tmp to that location and they filled it up and crashed mysql again.
After going over their configuration file there was a setting wrong that was allowing the mysql instance to try and user 1200% of ram. Mysql config was set to allocate 37G of ram. This mysql server only has 4G available. After we tuned the mysql config variables where only 3gig can be used at 1 time giving 1gig to apache and the os.
We believe this now resolves the issues with it crashing and will be monitoring mysql very closely with these new changes. This weekend will be perform an OPTIMIZE as many of the databases are fragmented. Remember Mysql2 is open for business if you want to create a database there and soon MySQL3 will be release.
Thank you for your patience and understanding during this past week.
Over the weekend all servers had the Operating System updated with patches and reboots were applied.
We apologize to you for our short notice but our ongoing security precautions we don't like to schedule downtime for these in advance because hackers in the past like to take advantage of this and try to hit the servers with the known exploits for the exact updates we were going to patch for.
