I had the same problem with 4.0.4, I downgraded to 3.23.52 because I
thought it was something with the unstable version. Is 4.0.4 also built
against the same static glibc?
regards
/Lars
>This problem is due to the glibc used by mysql AB for building binary ...
>
>Have a look to mysql 3.23.53 c
This problem is due to the glibc used by mysql AB for building binary ...
Have a look to mysql 3.23.53 change log :
<<
We've hopefully fixed the problem with spurious load spikes on Linux
> >systems when accessing the Database via TCP/IP. This was caused by
the
> >static glibc files we us
This problems are making me a bit tired, forgot to give you information
about the systems.
MySQL-3.23.52
dual pentium 700, 800MB ram
RedHat 6.1
Kernel 2.2.19-6.2.1smp
glibc-2.1.3-27
MySQL-3.23.52-Max
dual pentium 1.4Ghz, 2 GB ram
Redhat 7.3
Kernel 2.4.18-10smp
glibc-2.2.5-40
regards
/Lars
On
I'm managing two database servers, one 3.23.52 and one 3.23.52-Max
(using innodb tables on that one).
They are both running along fine until they suddently start to
accumulate a lot of treads (a lot ~= 200-300), the state of these
threads is mostly "closing" and "opening" tables. This drives up t
