Comment 12 for bug 1417810

@dbpercona do you consider these low values to justify the trigger of an assertion failure, especially one that has not happened until the latest release?

While I agree it may need tuning I am only surprised that such an error would occur now.

I'll investigate the tuning, thanks. I didn't think 100MB for a innodb_log_file_size was small, especially since the assertion error never occured when it was at its default 15M....