Bug #81654 Can not start MySQL with innodb_log_buffer_size if there is not enough memory
Submitted: 31 May 2016 7:55 Modified: 31 May 2016 14:07
Reporter: Shahriyar Rzayev Email Updates:
Status: Not a Bug Impact on me:
Category:MySQL Server: InnoDB storage engine Severity:S2 (Serious)
Version:5.7.12 OS:Any
Assigned to: CPU Architecture:Any

[31 May 2016 7:55] Shahriyar Rzayev
Starting MySQL with: 

From 5.7.6 max value is -> 4294967295


2016-05-31T07:49:19.795299Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2016-05-31T07:49:19.800796Z 0 [Note] InnoDB: Completed initialization of buffer pool
2016-05-31T07:50:18.837004Z 0 [ERROR] InnoDB: Cannot allocate 4294951448 bytes of memory after 60 retries over 60 seconds. OS error: Cannot allocate memory (12). Check 
if you should increase the swap file or ulimits of your operating system. Note that on most 32-bit computers the process memory space is limited to 2 GB or 4 GB.
2016-05-31 11:50:18 0x7f7926ba1740  InnoDB: Assertion failure in thread 140158317500224 in file ut0ut.cc line 935
InnoDB: Failing assertion: !m_fatal

How to repeat:
See description

Suggested fix:
Same as resizing innodb_buffer_pool_size online:

[31 May 2016 14:07] MySQL Verification Team

Thank you for your bug report. However, this is not a bug.

First of all, InnoDB has to round the number to the page boundaries.

Second, your system does not have virtual memory for that big a buffer.

Hence, not a bug.
[10 Jan 2017 11:37] MySQL Verification Team
Bug #84455 marked as duplicate of this
[29 Oct 2018 5:19] MySQL Verification Team
Bug #92963 marked as duplicate of this one