Bug #76147 Mem advisor on 'InnoDB Log Buffer Flushed To Disk After Each tx' is noisy
Submitted: 4 Mar 2015 15:21 Modified: 10 Mar 2015 4:52
Reporter: Morgan Tocker Email Updates:
Status: Verified Impact on me:
Category:MySQL Enterprise Monitor: Advisors/Rules Severity:S3 (Non-critical)
Version:3.0 OS:Any
Assigned to: CPU Architecture:Any

[4 Mar 2015 15:21] Morgan Tocker
Mem is suggesting I set innodb_flush_log_at_trx_commit=2, when I'm just using the default configuration.  I think calling this a warning is noisy.

How to repeat:
Warning in default install.

Suggested fix:
I have some suggested alternatives:

- Warn if innodb_flush_log_at_trx_commit=1 but sync_binlog!=1 (server is only "half durable"; doesn't make sense, since once you are willing to lose some data you can't tell which it is.)

- Warn if sync_binlog=1 but version is less than 5.6 (no group commit)

We have proposed to enable sync_binlog=1 in 5.7 so this ties in nicely.
[10 Mar 2015 4:52] MySQL Verification Team
Hello Morgan,

Thank you for the report.