Bug #54081 Limit/control/tune/make configurable/release QUAN memory usage
Submitted: 28 May 2010 22:55 Modified: 1 Jun 2010 9:35
Reporter: Roel Van de Paar Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Enterprise Monitor: Agent Severity:S2 (Serious)
Version:2.2.1.1721 OS:Any
Assigned to: CPU Architecture:Any

[28 May 2010 22:55] Roel Van de Paar
Description:
Memory Usage by the MySQL Enterprise Monitor Agent does not clear/decrease after Query Analyzer is disabled (and requires agent service restart to clear/reset the memory usage by the Agent)

This behavior occurs when the Query Analyzer is enabled, and after capturing some query data, the memory usage by the Agent goes up on a very large scale (anywhere from 50MB to 1500MB), and then after the Query Analyzer is disabled (due to very high memory usaged by the Agent) and it is confirmed that no new query data is collected, the Memory Usage by the Agent is shown to be plateau'd and not increasing nor decreasing but staying at the same high value.  Customer has to restart the Agent service in order to clear the memory usage by the Agent back to its normal 6-8MB.

If the agent service is running locally at the monitored MySQL database server, this behavior may adversely/negatively affect (slowdown) the performance of the monitor MySQL database server due to such high memory usage of the Agent, which will not go down even though no new query data is being collected (Query Analyzer being disabled).

How to repeat:
Use QUAN. Observe memory.

Suggested fix:
- Limit/control/tune and make configurable the QUAN memory usage
- Release memory when QUAN not in use
[1 Jun 2010 2:39] Enterprise Tools JIRA Robot
Diego Medina writes: 
Verified as described. Thanks for your bug report.
[1 Jun 2010 9:35] Mark Leith
This is a duplicate of Bug#40462 - closing.