Bug #46709 | MEM on Windows suggests undocumented value for innodb_flush_method | ||
---|---|---|---|
Submitted: | 13 Aug 2009 21:46 | Modified: | 18 Sep 2009 16:34 |
Reporter: | Ben Krug | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Enterprise Monitor: Advisors/Rules | Severity: | S3 (Non-critical) |
Version: | 2.1 | OS: | Windows |
Assigned to: | Andy Bang | CPU Architecture: | Any |
[13 Aug 2009 21:46]
Ben Krug
[18 Aug 2009 17:37]
Enterprise Tools JIRA Robot
Andy Bang writes: Pushed up to revision 301. It turns out that using innodb_flush_method=unbuffered *is* documented, but it's only relevant to version 4.1, and in particular to 4.1.9. I have updated the expression to check for version 4.1.9 and I have updated the more info links to point to the relevant sections of the 4.1 manual.
[24 Aug 2009 22:45]
Enterprise Tools JIRA Robot
Keith Russell writes: Patch installed in versions => 2.1.0.1096.
[25 Aug 2009 16:15]
Enterprise Tools JIRA Robot
Marcos Palacios writes: Verified fixed in advisor bundle 2.1.0.1096.
[18 Sep 2009 16:34]
Tony Bedford
An entry was added to the 2.1.0 changelog: MySQL Enterprise Monitor 2.1 advisors for Windows suggested using innodb_flush_method=unbuffered, which is an undocumented value. Only documented values should have been recommended.