Help with long REPAIR table
Grettings! I'm new to the list, and I hope this isn't off-topic. I've got a MyISAM table that is about 3.3 GB in size. The index is around 4.7GB. I started a REPAIR TABLE nnn QUICK last Sunday in a mysql session, and its still running. The index keeps getting updated, but I can't tell if it is near completion or not. It's bringing other database operations to a crawl & we need to get back to normal ASAP. We have other problems...low disk space, and only 512MB of RAM. We'll be rectifying those problems as soon as this REPAIR completesif it ever completes. Is there any way to tell how far along a REPAIR has gotten? Is it possible to interrupt the command, maybe by shutting down the database? Would that just put me in a position to REPAIR again after upgrading disk & RAM? Should it even take this long on a database of this size? TIA for any info/help you can lend.. Regards, tom. ___ Tom Mattison Econ Technologies, Inc. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MySQL 3.23.56 Memory Usage Problem
| 0 | | Com_show_master_status | 0 | | Com_show_open_tables | 0 | | Com_show_processlist | 0 | | Com_show_slave_status| 0 | | Com_show_status | 2 | | Com_show_innodb_status | 0 | | Com_show_tables | 0 | | Com_show_variables | 3 | | Com_slave_start | 0 | | Com_slave_stop | 0 | | Com_truncate | 0 | | Com_unlock_tables| 0 | | Com_update | 2395953| | Connections | 181301 | | Created_tmp_disk_tables | 0 | | Created_tmp_tables | 42 | | Created_tmp_files| 0 | | Delayed_insert_threads | 0 | | Delayed_writes | 0 | | Delayed_errors | 0 | | Flush_commands | 1 | | Handler_delete | 9 | | Handler_read_first | 1 | | Handler_read_key | 16906338 | | Handler_read_next| 2499823| | Handler_read_prev| 0 | | Handler_read_rnd | 1660 | | Handler_read_rnd_next| 26464 | | Handler_update | 2320880| | Handler_write| 6193404| | Key_blocks_used | 249376 | | Key_read_requests| 201172027 | | Key_reads| 12482200 | | Key_write_requests | 18954479 | | Key_writes | 19013760 | | Max_used_connections | 27 | | Not_flushed_key_blocks | 0 | | Not_flushed_delayed_rows | 0 | | Open_tables | 28 | | Open_files | 48 | | Open_streams | 0 | | Opened_tables| 34 | | Questions| 17332238 | | Select_full_join | 0 | | Select_full_range_join | 0 | | Select_range | 66 | | Select_range_check | 0 | | Select_scan | 32 | | Slave_running| OFF| | Slave_open_temp_tables | 0 | | Slow_launch_threads | 1 | | Slow_queries | 0 | | Sort_merge_passes| 0 | | Sort_range | 0 | | Sort_rows| 1660 | | Sort_scan| 43 | | Table_locks_immediate| 23076339 | | Table_locks_waited | 0 | | Threads_cached | 7 | | Threads_created | 49 | | Threads_connected| 1 | | Threads_running | 1 | | Uptime | 337415 | +--++ _______ Tom Mattison -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: MySQL 3.23.56 Memory Usage Problem
Thank you for the info. That certainly sounds like my problem. Time to switch back to the older kernel & see if things improve. Regards, tom. > -Original Message- > From: Philip Molter [mailto:[EMAIL PROTECTED] > Sent: Monday, August 18, 2003 12:19 PM > To: Tom Mattison > Cc: [EMAIL PROTECTED] > Subject: Re: MySQL 3.23.56 Memory Usage Problem > > > On Mon, Aug 18, 2003 at 12:10:16PM -0400, Tom Mattison wrote: > : Greetings List, > : > : I'm running a dedicated MySQL server on a Dell PE 2550, dual proc. 4GB > : RAM. Its using the Dell PERC 3/Di Scsi RAID controller with > 18GB disks. I > : running RH 7.3 with the latest updates(Kernel 2.4.20-19.7smp). > The MySQL > : version is the rpm currently being provided by the RH updates. > I have been > : trying to tune the MySql daemon for a week now to prevent swapping. No > : matter what I do, I still end up with about 60GB of used swap space. > : > : Any suggestions on what I'm doing wrong? TIA for any > suggestions/help! > > That's not MySQL causing the problem, that's Linux's memory > management. Of course, in your data below, you have 60MB of used > swap, not 60GB. > > If you want to track the issue with Redhat, check out bug 89226 on > their bugzilla website. > > * Philip Molter > * Texas.net Internet > * http://www.texas.net/ > * [EMAIL PROTECTED] > > -- > 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]
