Successful doublewrite recovery should not be a warning

Bug #1622985 reported by Laurynas Biveinis on 2016-09-13
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server
Status tracked in 5.7
5.5
Medium
Laurynas Biveinis
5.6
Medium
Laurynas Biveinis
5.7
Medium
Laurynas Biveinis

Bug Description

Crash testcases might fail with the following, 5.6 trunk:

rpl.rpl_sync 'stmt' w2 [ fail ] Found warnings/errors in server log file!
        Test ended at 2016-08-31 13:28:07
line
InnoDB: Warning: database page corruption or a failed
^ Found warnings in /mnt/workspace/percona-server-5.6-trunk/BUILD_TYPE/debug/Host/centos6-64/build/mysql-test/var/2/log/mysqld.2.err
ok

This does not indicate any real problem but is rather a sign of expected doublewrite buffer operation. Instead of adding a suppression to each affected testcase, the message should be downgraded from Warning severity, similar to WebScaleSQL: https://github.com/webscalesql/webscalesql-5.6/commit/71abb720c08b640ecd85c849c1ee8f90892b6cad

This will make bug 16139886 fix obsolete and it should be reverted

summary: - Spurious testcase warnings if crash recovery used doublewrite
+ Successful doublewrite recovery should not be a warning
tags: added: ci innodb upstream

Seen on 5.5 too:

main.group_commit_crash w2 [ fail ] Found warnings/errors in server log file!
        Test ended at 2017-05-04 08:43:15
line
InnoDB: Warning: database page corruption or a failed
^ Found warnings in /mnt/workspace/percona-server-5.5-trunk/BUILD_TYPE/debug/Host/debian-wheezy-x32/mysql-test/var/2/log/mysqld.1.err
ok

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers