MySQL Bugs: #54355: innodb_fast_shutdown is collected with a value of ON, leads to type exception

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:	None
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

Description:
Collecting the variable innodb_fast_shutdown with a value of ON leads to the following exception in the service manager:

2010-06-07 16:18:40,445 ERROR [http-18080-1:com.mysql.inventory] ignoring attribute innodb_fast_shutdown for object {mysql}.{variables}.{252e71b5-d846-47a3-9119-ae8aaa052dba}
com.mysql.etools.exception.InvalidValueForTypeException: E0815: InvalidValueForTypeException: [ON, long, unknown]
	at com.mysql.etools.monitor.pom.AttributeValue.translateToLongWithTruncation(AttributeValue.java:163)
	at com.mysql.etools.monitor.pom.ValueType.parseValue(ValueType.java:171)
	at com.mysql.etools.monitor.pom.ValueType.canonicalValue(ValueType.java:138)
[... uninteresting stack trace omitted...]

innodb_fast_shutdown should normally have values of 0, 1, or 2, not ON/OFF.

How to repeat:
Needs clarification on the mysqld version used.

Suggested fix:
Either rectify the value of innodb_fast_shutdown (is ON/OFF actually allowed in some version?) during collection or determine the source of the unexpected value (mysqld version) and support that directly.

Kay: mysqld version in this particular case was 4.1.22

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.

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.