Sinisa Milivojevic a écrit :
>
> Joseph Bueno writes:
> > Hello,
> >
> > I posted message below a few hours ago.
> > Since then, I have tried to find how fast indexes become corrupt.
> > I have run a CHECK TABLE <table> QUICK
> > on different tables in my database and run a
> > REPAIR TABLE <table> when an error is reported followed
> > by a CHECK TABLE a few seconds later. Here is the output of
> > both commands:
> >
> > mysql> repair table message;
> > +-------------------+--------+----------+----------+
> > | Table | Op | Msg_type | Msg_text |
> > +-------------------+--------+----------+----------+
> > | rencontre.message | repair | status | OK |
> > +-------------------+--------+----------+----------+
> > 1 row in set (1 min 47.13 sec)
> >
> > mysql> check table message quick;
> >
>+-------------------+-------+----------+------------------------------------------------+
> > | Table | Op | Msg_type | Msg_text
> > |
> >
>+-------------------+-------+----------+------------------------------------------------+
> > | message | check | error | Key 2 doesn't point at same
> > records that key 1 |
> > | rencontre.message | check | error | Corrupt |
> >
>+-------------------+-------+----------+------------------------------------------------+
> > 2 rows in set (1.75 sec)
> >
> > How is is possible that a table becomes corrupt so fast ?
> > What information should I send you in order to help me ?
> >
> > I am running mysqld Ver 3.23.30-gamma for pc-linux-gnu
> > on i686 on a RedHat 6.2 server (bipro PIII 733/2Gb RAM)
> >
> > We did not have these problems during our integration tests
> > so it may be possible that they are related to the high load
> > on the production server (between 250 and 300 queries/s).
> >
> > Thanks for your help
> > --
> > Joseph Bueno
>
> Hi!
>
> Can you find out commands that will always lead to the table
> corruption.
>
I really don't know how to do it. We can't reproduce it on our
development server and it seems rather impractical to run a
myisamchk after each insert/update on production server. There
are several hundred of users using it when corruptions occur
and they would be very angry if the server becomes unusable
(some already are, we got more than 400 emails of complaints
in less than 2 hours after one table corruption made them think
they had lost their data).
I have set up a cron job that stops mysqld and run a myisamchk
every half an hour. That the best I can do without hurting too much
the performance but it will not help to pinpoint the exact
query that corrupts the table.
> Only if you can make a reproducible test, then we could help you.
>
> Are you using our binary version ??
Yes, from MySQL-3.23.30-1.i386.rpm
BTW, are there any known issues with:
- glibc from RedHat 6.2 (I have checked Red Hat site there is
no update for it)
- MySQL with SMP (I have been told to try with one CPU only
but I cannot try until monday)
>
> Regards,
>
> Sinisa
>
> ____ __ _____ _____ ___ == MySQL AB
> /*/\*\/\*\ /*/ \*\ /*/ \*\ |*| Sinisa Milivojevic
> /*/ /*/ /*/ \*\_ |*| |*||*| mailto:[EMAIL PROTECTED]
> /*/ /*/ /*/\*\/*/ \*\|*| |*||*| Larnaka, Cyprus
> /*/ /*/ /*/\*\_/*/ \*\_/*/ |*|____
> ^^^^^^^^^^^^/*/^^^^^^^^^^^\*\^^^^^^^^^^^
> /*/ \*\ Developers Team
Thanks for your help
--
Joseph Bueno
NetClub/Trader.com
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
