MySQL Bugs: #76932: comment of innodb_buffer_pool_chunk

Bug #76932	comment of innodb_buffer_pool_chunk_size is incorrect
Submitted:	4 May 2015 14:56	Modified:	4 May 2015 15:43
Reporter:	zhai weixiang (OCA)	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S3 (Non-critical)
Version:	5.7.7	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
$cat VERSION
MYSQL_VERSION_MAJOR=5
MYSQL_VERSION_MINOR=7
MYSQL_VERSION_PATCH=7
MYSQL_VERSION_EXTRA=-rc

$cat storage/innobase/handler/ha_innodb.cc  | grep 'MYSQL_SYSVAR_ULONG(buffer_pool_chunk_size' -A 6
static MYSQL_SYSVAR_ULONG(buffer_pool_chunk_size, srv_buf_pool_chunk_unit,
  PLUGIN_VAR_RQCMDARG | PLUGIN_VAR_READONLY,
  "Size of a single memory chunk within each buffer pool instance"
  " for resizing buffer pool. Online buffer pool resizing happens"
  " at this granularity. 0 means disable resizing buffer pool.",
  NULL, NULL,
  128 * 1024 * 1024, 1024 * 1024, LONG_MAX, 1024 * 1024);

Actually the min value of innodb_buffer_pool_chunk_size is 1024 * 1024 rather than 0.

How to repeat:
read the code

Suggested fix:
correct it.

Actually, the values in the struct initialization are contradictory with the text field. Hence, either a text should be changed or the integer initialization. In the second case, documentation has to be updated too. This is not a high severity issue.

Verified.