Thank you Sinisa,
I actually did try the upgade, but rapidly reverted due to errors
such as these:
mysqld got signal 11;
stack range sanity check, ok, backtrace follows
0x812cfea
0x809f541
0x809da87
:
:
etc
AND...
read_const: Got error 127 when reading table ./....
read_next_with_key: Got error 134 when reading table ./....
read_cost: Got error 134 when reading table ./...
(sometimes dozens and dozens repeated.. re-optimizing the
table may cure them for a short while. Again this was only
on the largest/busiest few tables).
So I went back to the previous last snap of the 3.22
On the threads / glibc issue: I'm using the *statically linked*
version of mysqld from your download page, in both 3.23 (that gave
erros above), and 3.22 (that gives corrupt indexes), therefore my
understanding was that glibc / linux threads issues would not
be an issue? is that understanding incorrect?
What else in a 2.2.14 SMP kernel can cause a problem for
statically linked 3.22 or 3.23 ? I would need some clearer
explanation before making a new kernel.
By the way, we bought the $1000 support license last week,
but so far have not got into your supportwizard site.. I've
emailed support@ about this. Just so you don't think we're
not willing to pay for some attention.
thanks
-Justin
On Sun, Mar 11, 2001 at 02:21:55PM +0200, Sinisa Milivojevic wrote:
> Justin writes:
> > What is your key buffer size? In my case, key buffer size is set
> > to 384mb .. and mysqld starts out small, perhaps 18mb and grows
> > within a day to 100mb, and within a few days to pretty much 300+mb
> > ..so it is doing what one would expect it to.
> >
> > The other mem parameters combine in ways explained in the memory
> > usage document.. so depending on those, I expect 300 threads could
> > eat a lot of memory, which is not returned to the OS.
> >
> > -Justin
> >
>
>
> HI!
>
> First of all, please listen to the advice on upgrading to the latest
> 3.23 binary and converting your tables to MyISAM format with a script
> provided.
>
> Second, there have been some problems with Linux SMP under high load
> which seem to be solved with 2.4.* kernel and 2.2.* glibc.
>
>
> Regards,
>
> Sinisa
>
> ____ __ _____ _____ ___ == MySQL AB
> /*/\*\/\*\ /*/ \*\ /*/ \*\ |*| Sinisa Milivojevic
> /*/ /*/ /*/ \*\_ |*| |*||*| mailto:[EMAIL PROTECTED]
> /*/ /*/ /*/\*\/*/ \*\|*| |*||*| Larnaca, Cyprus
> /*/ /*/ /*/\*\_/*/ \*\_/*/ |*|____
> ^^^^^^^^^^^^/*/^^^^^^^^^^^\*\^^^^^^^^^^^
> /*/ \*\ Developers Team
--
Justin Beech http://www.dslreports.com
Phone:212-269-7052 x252 FAX inbox: 212-937-3800
mailto:[EMAIL PROTECTED] --- http://dslreports.com/contacts
---------------------------------------------------------------------
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
