Bug #60777 graph not fixed for innodb_buffer_pool_instances > 0
Submitted: 6 Apr 2011 12:05 Modified: 26 Apr 2011 19:50
Reporter: Daniël van Eeden Email Updates:
Status: Closed Impact on me:
Category:MySQL Enterprise Monitor: Documentation Severity:S2 (Serious)
Version: OS:Any
Assigned to: CPU Architecture:Any
Triage: Needs Triage: D3 (Medium)

[6 Apr 2011 12:05] Daniël van Eeden
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:
The changelogs indicate that it should be working, but the bug report suggests that it relies on a server with a fix for Bug #58461 (Merged in 5.5.9).

1. Clearly indicate that it only works for 5.5.9 and newer (if that's true)

2. The latest enterprise release from edelivery.oracle.com for 5.5. is 5.5.8. So please release a new build if that's needed.

3. If upgrading is required, create an upgrade rule for that.
[6 Apr 2011 13:08] Valeriy Kravchuk
Item 1 in "Suggested fix" section is a documentation request. Item 3 looks like a MEM feature request. Item 2 is a known problem that will be fixed eventually (5.5.11 is coming soon/ready anyway).

So, please, decide what is this report about (1 or 3), and open a new one for other item of these two.
[11 Apr 2011 13:17] Daniël van Eeden
Consider this a documentation request.
[11 Apr 2011 13:20] Daniël van Eeden
This is related to Bug #60831
[26 Apr 2011 19:50] John Russell
Added to 2.3.2 changelog.