ry corruption.
Did you receive the exact same assertion failure also on x86?
How easy is it to repeat the crash?
I have now added some diagnostic code to InnoDB-4.1.15.
Regards,
Heikki
- Original Message -
From: "David Sparks" <[EMAIL PROTECTED]>
Newsgroups: mailin
Hello.
Sorry for a delayed answer. Could you provide a whole error message with
a resolved stack trace? Check if the problem remains when you switch to
the official binaries.
David Sparks wrote:
> Gleb Paharenko wrote:
>
>> Hello.
>>
>> > = 77591546 K
>>
>>
>> Really - somet
Gleb Paharenko wrote:
>Hello.
>
> > = 77591546 K
>
>
>Really - something is wrong with your memory settings - MySQL is using
>about 77G of memory
>
Unfortunately getting the daemon to not go above the theoretical limit
has tanked performance. In reality I never see the daemon go above 45%
RAM us
I forgot to include the output of show variables and show status in the
last message :(
mysql> show variables\G
*** 1. row ***
Variable_name: back_log
Value: 50
*** 2. row ***
Variable_name:
Gleb Paharenko wrote:
Hello.
> = 77591546 K
Really - something is wrong with your memory settings - MySQL is using
about 77G of memory (or you have such a cool server :)! Please send the
output of 'SHOW VARIABLES' statement, 'SHOW STATUS' statement and your
configuration file. Include the a
Hello.
> = 77591546 K
Really - something is wrong with your memory settings - MySQL is using
about 77G of memory (or you have such a cool server :)! Please send the
output of 'SHOW VARIABLES' statement, 'SHOW STATUS' statement and your
configuration file. Include the amount of physica
mysql usually crashes when being shutdown. The machine is a dual AMD64
w 8GB RAM running mysql-4.1.14 on Gentoo linux with a ~40GB database. I
had similar crashes running 4.0.24 on an x86 running a ~275GB database.
I always use `mysqladmin shutdown` rather than the init scripts to
shutdown t
