Hi,

Try also to download 4.0.5a (not 4.0.5), this version could solve your load
problem (due to a problem with the glibc used during the build)

Regards,
  Jocelyn

----- Original Message -----
From: "Josh Marcus" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, December 06, 2002 2:16 AM
Subject: abnormally high load under 4.04


> Recently, I upgraded some moderately taxed mysql servers from 3.23.49a to
> 4.0.4  (all installed via redhat rpms downloaded from mysql.com).  The
> motivation for the upgrade was actually that replication seems a little
flaky
> under 3.23.49a.  For example, we've had unexplained corrupt binlog issues.
> (If anyone has any advice on this, that'd be appreciated.)
>
> About 20 hours after the upgrade, and then periodically after that, the
machine
> the server was on would grind to a halt with a load of 100-200.  It was
> difficult to grab any information at all about what was goin' on
considering
> the load.  Once mysqld was killed & restarted, things would return to
normal
> until some period later when the machine would grind to a halt once again.
>
> Any advice?  What should we looking for?  One issue might be that we have
> the maximum number of connections set way too high for the 1GB of memory
> the box has.
>
> --j
>
> ---------------------------------------------------------------------
> 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
>
>
>
>


---------------------------------------------------------------------
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

Reply via email to