Bug #29389 InnoDB Log Buffer Flushed To Disk After Each Transaction

Submitted:	27 Jun 2007 14:20	Modified:	10 Jul 2007 13:51
Reporter:	Kristian Koehntopp	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Advisors/Rules	Severity:	S3 (Non-critical)
Version:	1.1.0	OS:	Any
Assigned to:	Andy Bang	CPU Architecture:	Any

Description:
WARNING Alert - InnoDB Log Buffer Flushed To Disk After Each Transaction  (v 1.0 *)  

Thresholds
 Critical Alert = not set
 Warning Alert = 1
 Info Alert = not set 

Frequency
06:00

Expression
%innodb_flush_log_at_trx_commit% == THRESHOLD

Evaluated Expression
1 == 1

This fires even on machines where innodb is disabled.

How to repeat:
Start a machine with skip-innodb, schedule rule. See wrong advice.

Suggested fix:
(%have_innodb% == "YES") &&  (%innodb_flush_log_at_trx_commit% == THRESHOLD%innodb_flush_log_at_trx_commit% == THRESHOLD)

Committed revision 6469.

Fixed the expression that was committed, which was using '==' instead of '=':

mysql> select ('yes' == 'yes') && (1 == 1);
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '== 'yes') && (1 == 1)' at line 1

ooops, reverted previous commits! :)

Verified fixed in 1.2.0.5601

Page generated in 0.050 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.