Bug #61194 Non heart chart MEM advisors disabled or unscheduled are still run on startup

• Submitted: 17 May 2011 8:13
• Modified: 17 May 2011 17:09
• Reporter: Arnaud Adant
• Status: Closed
• Category: MySQL Enterprise Monitor: Documentation
• Severity: S3 (Non-critical)
• Version: 2.3.3
• OS: Any
• CPU Architecture: Any
• Tags: advisor, mem, rule

[17 May 2011 8:13] Arnaud Adant

Description:
The manual says that MEM advisors will be "no longer" run if disabled or unscheduled except for the heart chart ones.

http://dev.mysql.com/doc/mysql-monitor/2.3/en/mem-unscheduling-advisors.html

There should be a note stating that these advisors will still be run on startup
(discovery mode).

How to repeat:
- Disable or unschedule a non heart chart advisor.
- Activate the general query log on the target test server.
- see that the query behind the advisor is still run.

Suggested fix:
Use custom.xml.

This will disable 2 advisors (auto_increment_limit and tables_no_myisam_index_stats).

<class>
<namespace>mysql</namespace>
<classname>auto_increment_limit</classname>
<precondition><![CDATA[SELECT
1=0]]></precondition>
<query><![CDATA[select 1]></query>
</class>

<class>
<namespace>mysql</namespace>
<classname>tables_no_myisam_index_stats</classname>
<precondition><![CDATA[SELECT
1=0]]></precondition>
<query><![CDATA[select
1]></query>

[17 May 2011 17:09] John Russell

Added to documentation: 

Advisors, even those that are unscheduled or disabled, still run 
during discovery mode when MySQL Enterprise Monitor starts, and when the 
dashboard runs the "inventory" process.