Bug #54355 | innodb_fast_shutdown is collected with a value of ON, leads to type exception | ||
---|---|---|---|
Submitted: | 9 Jun 2010 7:32 | Modified: | 9 Jun 2010 16:29 |
Reporter: | Kay Roepke | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Enterprise Monitor: Server | Severity: | S3 (Non-critical) |
Version: | 2.2.1.1721 (server), 2.2.1.1717 (agent) | OS: | Any |
Assigned to: | MEM Agent Devs | CPU Architecture: | Any |
[9 Jun 2010 7:32]
Kay Roepke
[9 Jun 2010 8:43]
Roel Van de Paar
Kay: mysqld version in this particular case was 4.1.22
[9 Jun 2010 16:26]
Enterprise Tools JIRA Robot
Andy Bang writes: innodb_fast_shutdown is reported as ON/OFF in MySQL 4.1, but as 1/0 in 5.0 and 5.1.
[9 Jun 2010 16:29]
Enterprise Tools JIRA Robot
Andy Bang writes: Fixing this would require special-case code in MEM to handle the fact that the MySQL server reports a value as a string in 4.1, but as a number in 5.0 and 5.1. Because 4.1 is currently EOL, we recommend that the customer upgrade to a supported release and the problem will go away.