Bug #67091 MySQL service wont start with large buffer pool.
Submitted: 4 Oct 2012 21:10 Modified: 10 Oct 2012 8:49
Reporter: Abhijit Mori Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S5 (Performance)
Version:5.0.80 OS:Windows (2008 server)
Assigned to: CPU Architecture:Any
Tags: InnoDb buffer pool.

[4 Oct 2012 21:10] Abhijit Mori
Description:
I would like to know what are the maximum possible values for InnoDb buffer pool. Have a server with 128GB RAM and I tried to assign 70G as buffer pool and Mysql service wont start. With 60GB as buffer pool the service will come up but sometimes there is assertion failure. Get below error message.

121004 10:10:52InnoDB: Assertion failure in thread 660 in file .\os\os0sync.c line 330
InnoDB: Failing assertion: CloseHandle(event->handle)
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Thread 1600 stopped in file d:\mysql-5.0.80-winbuild\mysql-enterprise-5.0.80-build\innobase\include\sync0sync.ic line 111
InnoDB: Thread 668 stopped in file .\os\os0sync.c line 389
121004 10:10:52 - mysqld got exception 0xc0000005 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=134217728
read_buffer_size=524288
max_used_connections=144
max_connections=350
threads_connected=25
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 489472 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation

How to repeat:
Increasing InnoDb buffer pool. No idea..
[5 Oct 2012 3:09] Calvin Sun
The problem is fixed in MySQL 5.5.
[5 Oct 2012 18:34] Abhijit Mori
Thanks Calvin.

Do you know what is causing this? And what will be safe value of InnoDb buffer pool?  Or does it even make a difference. I mean if the issue is not just related with buffer pool allocation and something else.

Appreciate your Help!!
[6 Oct 2012 14:13] MySQL Verification Team
Number of handles used in 5.0 is excessive, and likely hits 16.7 million threshold.
Take a look at http://bugs.mysql.com/bug.php?id=52102
[9 Oct 2012 21:00] Abhijit Mori
That definitely makes sense. I was able to see the issue happening and MySQL using almost all the possible handles, after which it crashed. I am going to try with 55 GB of buffer pool along with thought of upgrading to MySQL 5.5.8.

Link was helpful Shane. Thanks.
[10 Oct 2012 8:49] MySQL Verification Team
Hi, I'll close this bug then, as problem is solved in recent versions.
Just a side note, please never consider 5.5.8 as a solution.
Rather download 5.5.28 or whatever is the more recent version on dev.mysql.com.