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 Email Updates:
Status: Closed Impact on me:
Category:MySQL Enterprise Monitor: Documentation Severity:S3 (Non-critical)
Version:2.3.3 OS:Any
Assigned to: CPU Architecture:Any
Tags: advisor, mem, rule

[17 May 2011 8:13] Arnaud Adant
The manual says that MEM advisors will be "no longer" run if disabled or unscheduled except for the heart chart ones.


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).

<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.