Successful doublewrite recovery should not be a warning
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
Fix Released
|
Medium
|
Laurynas Biveinis | |||
5.6 |
Fix Released
|
Medium
|
Laurynas Biveinis | |||
5.7 |
Fix Released
|
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/
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:/
This will make bug 16139886 fix obsolete and it should be reverted