Re: repairing tables on 129.47.9.130 (marketing intel)

From: Ty Heath <ty.heath_at_mac.com>
Date: Sun, 22 Apr 2007 12:12:50 -0700

It doesn't matter. It does lock the table you are repairing, but the
mysql server should function normally otherwise.

Ty

On Apr 22, 2007, at 11:47 AM, Dylan Douglas wrote:

> Does the mysql db have to be closed down before running this script
> and then restarted after? Or does the script take care of it? Or
> does it not matter?
>
> -D
>
> ----------
> Dylan Douglas
> MediaDefender
>
> From: Ty Heath
> Sent: Sun 4/22/2007 11:48 AM
> To: Dylan Douglas; Ivan Kwok; Danny Song; Jay Mairs; Nainesh
> Solanki; Stefan Kaczmarek
> Subject: repairing tables on 129.47.9.130 (marketing intel)
>
> Okay, repairing large tables crashes mysql for whatever reason. It
> uses too much ram and dies. So they have to be repaired externally.
> I have created a script on that server for this purpose that uses
> myisamchk. To use it just execute something like:
>
> repairdb /var/lib/mysql/ares_supply/ares_dht_audio_meta_data
>
> You would change the database and table name as appropriate, this
> will keep the server from crashing and a nasty circular pattern of 1
> repair causing other tables to need repair.
>
> This will spawn a seperate process independent of the mysql server
> process and allows us to pass options to limit memory usage etc.
>
> Ty
Received on Fri Sep 14 2007 - 10:56:07 BST

This archive was generated by hypermail 2.2.0 : Sun Sep 16 2007 - 22:19:48 BST