InnoDB Buffer Pool Configuration mysql>  SET GLOBAL innodb_buffer_pool_size=402653184; mysql>  SHOW STATUS WHERE Variable_name=’InnoDB_buffer_pool_resize_status’; +----------------------------------+----------------------------------+ | Variable_name | Value | +----------------------------------+----------------------------------+ | Innodb_buffer_pool_resize_status | Resizing also other hash tables. | +----------------------------------+----------------------------------+ [Note] InnoDB: Resizing buffer pool from 134217728 to 4294967296. (unit=134217728) [Note] InnoDB: disabled adaptive hash index. [Note] InnoDB: buffer pool 0 : 31 chunks (253952 blocks) was added. [Note] InnoDB: buffer pool 0 : hash tables were resized. [Note] InnoDB: Resized hash tables at lock_sys, adaptive hash index, dictionary. [Note] InnoDB: completed to resize buffer pool from 134217728 to 4294967296. [Note] InnoDB: re-enabled adaptive hash index. [Note] InnoDB: Resizing buffer pool from 4294967296 to 134217728. (unit=134217728) [Note] InnoDB: disabled adaptive hash index. [Note] InnoDB: buffer pool 0 : start to withdraw the last 253952 blocks. [Note] InnoDB: buffer pool 0 : withdrew 253952 blocks from free list. tried to relocate 0 pages. (253952/253952) [Note] InnoDB: buffer pool 0 : withdrawn target 253952 blocks. [Note] InnoDB: buffer pool 0 : 31 chunks (253952 blocks) was freed. [Note] InnoDB: buffer pool 0 : hash tables were resized. [Note] InnoDB: Resized hash tables at lock_sys, adaptive hash index, dictionary. [Note] InnoDB: completed to resize buffer pool from 4294967296 to 134217728. [Note] InnoDB: re-enabled adaptive hash index. 3114 Online Buffer Pool Resizing Internals The resizing operation is performed by a background thread. When increasing the size of the buffer pool, the resizing operation: This example shows notes that are logged when decreasing the size of the buffer pool: Buffer pool resizing progress is also logged in the server error log. This example shows notes that are logged when increasing the size of the buffer pool: The  Innodb_buffer_pool_resize_status  reports buffer pool resizing progress. For example: Nested transactions could fail if initiated after the buffer pool resizing operation begins. Active transactions and operations performed through  InnoDB  APIs should be completed before resizing the buffer pool. When initiating a resizing operation, the operation does not start until all active transactions are completed. Once the resizing operation is in progress, new transactions and operations that require access to the buffer pool must wait until the resizing operation finishes. The exception to the rule is that concurrent access to the buffer pool is permitted while the buffer pool is defragmented and pages are withdrawn when buffer pool size is decreased. A drawback of allowing concurrent access is that it could result in a temporary shortage of available pages while pages are being withdrawn. The buffer pool size must be equal to or a multiple of innodb_buffer_pool_chunk_size  *  innodb_buffer_pool_instances . Changing those variable settings requires restarting the server. Note Note Monitoring Online Buffer Pool Resizing Progress