Good morning, Steffan - Can you post some details about what you mean when you say the tables are damaged? What makes you say that / what are the signs/symptoms?
Does the server process crash, or stop responding? Do you see anything in the error logs? Do you have enough disk space for temp tables? Can you post the output of SHOW STATUS; after it has been running for a while as well ? If the server truly is just being overloaded, then an analysis of the problematic/slow queries would be in order. Could be that better queries and/or additional indices could help. Still, I'd like to know more about what is happening with the damaged tables. I don't know of any specific problems with 5.0.18, but it generally doesn't hurt to upgrade to the latest production release. The release notes are online so you could search for relevant fixes before deciding to download and upgrade. Dan On 11/8/06, Steffan A. Cline <[EMAIL PROTECTED]> wrote:
I am having an issue with MySQL running on Mac OS X. Currently the version as stated 5.0.18 on a dual G4 Xserve with 1gb of ram. MySQL is mainly the only thing running on this server. I am trying to track down an issue in which MySQL is being overloaded and it consistently damages the same one or two tables. I am trying to narrow down the issue to the web service connecting to MySQL or MySQL itself. When I check the status I see a ton of locks and unauthenticated connections. Any suggestions of what to look for on the MySQL side? It seems rather odd that being overloaded is that it damages the tables. There is no replication or auto backups in place with this that could cause these issues. Some of the queries thrown are indeed big ones and do require many ticks to calculate but still, what is left? I just made some changes to the config and this is now the base of what I have: # The MySQL server [mysqld] port = 3306 socket = /tmp/mysql.sock skip-locking key_buffer = 256M max_allowed_packet = 50M table_cache = 256 sort_buffer_size = 1M read_buffer_size = 1M read_rnd_buffer_size = 4M myisam_sort_buffer_size = 64M #thread_cache_size = 8 query_cache_type = 1 query_cache_size = 128M query_cache_limit = 128M # added the next few lines for debugging all the way to the next comment skip-name-resolve interactive_timeout = 300 wait_timeout = 300 max_connections = 250 thread_cache_size = 40 log_error = /var/log/mysqld-error.log log_slow_queries = /var/log/mysqld-slow.log # Try number of CPU's*2 for thread_concurrency thread_concurrency = 8 Could it be the version of MySQL that is causing the damage? I did a fsck on the drive and all comes back fine. What's left? Thanks Steffan --------------------------------------------------------------- T E L 6 0 2 . 5 7 9 . 4 2 3 0 | F A X 6 0 2 . 9 7 1 . 1 6 9 4 Steffan A. Cline [EMAIL PROTECTED] Phoenix, Az http://www.ExecuChoice.net USA AIM : SteffanC ICQ : 57234309 Lasso Partner Alliance Member --------------------------------------------------------------- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
