Sporadic percona_changed_page_bmp testcase warnings
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Low
|
Laurynas Biveinis | ||
5.1 |
Invalid
|
Low
|
Unassigned | ||
5.5 |
Invalid
|
Low
|
Unassigned | ||
5.6 |
Fix Released
|
Low
|
Laurynas Biveinis |
Bug Description
percona_
2013-10-05 19:17:51 19199 [ERROR] InnoDB: We scanned the log up to 29651456. A checkpoint was at 29651809 and the maximum LSN on a database page was 0. It is possible that the database is now corrupt!
This warning happens during a server startup of one of the server restarts by the testcase (4th restart in the testcase). This restart is preceded by a relatively big data write, and the error log shows that the server shutdown did not fully complete, but rather was killed by MTR shutdown_server timeout.
It is likely that this is caused by buffer pool flush not being able to flush all the written data in the allocated time.
The fix is to increase the shutdown_server timeout value to allow for a clean shutdown.
Related branches
- Vadim Tkachenko: Approve
-
Diff: 255 lines (+69/-21)6 files modifiedPercona-Server/mysql-test/suite/innodb/t/percona_changed_page_bmp.test (+9/-9)
Percona-Server/storage/innobase/buf/buf0flu.cc (+11/-3)
Percona-Server/storage/innobase/buf/buf0lru.cc (+5/-2)
Percona-Server/storage/innobase/include/buf0flu.h (+10/-0)
Percona-Server/storage/innobase/include/buf0flu.ic (+21/-0)
Percona-Server/storage/innobase/log/log0log.cc (+13/-7)
tags: | added: bitmap ci xtradb |
Increasing timeouts uncovered a shutdown deadlock instead. The 10 second timeout still might be too short for loaded hosts, but this is best kept untouched for now.