Bug #60831 graph not fixed for innodb_buffer_pool_instances > 0
Submitted: 11 Apr 2011 13:20 Modified: 11 Apr 2011 14:06
Reporter: Daniël van Eeden Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Enterprise Monitor: Advisors/Rules Severity:S3 (Non-critical)
Version:2.3.2.2055 OS:Any
Assigned to: CPU Architecture:Any

[11 Apr 2011 13:20] Daniël van Eeden 
Description:
From http://dev.mysql.com/doc/mysql-monitor/2.3/en/mem-news-2-3-2.html:
"The graph for the InnoDB buffer pool now reports correct totals when
innodb_buffer_pool_instances is set to a value greater than 0. (Bug #58332)"

After upgrading the service manager from 2.3.1 to 2.3.2 and doing a reinstall for 2.3.2
for the agent the graph still contains values for 1 buffer pool instance.

The monitored server is running 5.5.8 (Enterprise Release)

How to repeat:
Monitor server with multiple buffer pools.

Suggested fix:
 If upgrading is required, create an upgrade rule for that.

This is related to Bug #60777
[11 Apr 2011 14:06] Valeriy Kravchuk 
Here we have a reasonable feature request for a new advisor/rule (suggesting upgrade).