Bug #77431 why spam INDIVIDUAL BUFFER POOL INFO sections in show engine innodb status?

• Submitted: 22 Jun 2015 12:17
• Modified: 3 Jul 2015 8:54
• Reporter: Shane Bester (Platinum Quality Contributor)
• Status: Verified
• Category: MySQL Server: InnoDB storage engine
• Severity: S4 (Feature request)
• Version: 5.6.25
• OS: Any
• CPU Architecture: Any

[22 Jun 2015 12:17] Shane Bester

Description:
SHOW ENGINE INNODB STATUS outputs the total first, then again for each individual instance.

----------------------
BUFFER POOL AND MEMORY
----------------------
Total memory allocated 21463040000; in additional pool allocated 0
.....
----------------------
INDIVIDUAL BUFFER POOL INFO
----------------------
---BUFFER POOL 0
..
---BUFFER POOL 1
..
---BUFFER POOL 2
..
---BUFFER POOL 3
...
---BUFFER POOL 32

How to repeat:
start mysqld with many innodb-buffer-pool-instances and try to read 
'show engine innodb status';

Suggested fix:
my eyes cannot handle this lot anymore.   since there is no control over what instance is used or not,  why care about each instance?

you can fetch that data from information_schema.INNODB_BUFFER_POOL_STATS anyway.

also,  grepping the long semophore wait innodb outputs from error log for certain information is not feasible now because the instances duplicate the value.

[3 Jul 2015 8:54] MySQL Verification Team

Hello Shane,

Thank you for the feature request!

Thanks,
Umesh