MySQL Enterprise Monitor Agent having memory leaks

I’ve recently updated MySQL Enterprise Monitor on few boxes to the most recent version. Apparently, since Oracle acquired Sun, Enterprise team has lowered its quality standards. The agent (in agent,proxy mode) kept leaking memory at pace of about 1 Gb per hour (got up to 5gbs before we’ve noticed).

The offending binary was:

mysqlmonitoragent-2.1.1.1144-linux-glibc2.3-x86-64bit-installer.bin

I find it extremely disappointing, as long as I wouldn’t care about Monitor Server going down, I expect agents to be extremely stable, as their failure can affect production services. With agent deployed on the same box as the database, it’s easy to redirect the traffic to port of the real db in case if it crashed, however if agent consumed memory dedicated for MySQL, it would cause the database & other services to crash.

Share
    • I
    • February 17th, 2012 10:02pm

    How did this issue resolve? Did you get it sorted with Oracle?

    We’re having issues with one of our instances: it’s been running for 3 days now and the memory used is 1,1 GB. We’re trying to investigate this with Oracle. But, we’re running Solaris here…

    • Maciej Wiercinski
    • February 20th, 2012 7:23pm

    We have got rid of MySQL Enterprise agents and moved to other tools like pt-query-digest.

  1. No trackbacks yet.