Testcases restart in InnoDB read only mode incorrectly | Intermittent errors in the error log on innodb.percona_log_archive_ro
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
Invalid
|
Undecided
|
Unassigned | |||
5.6 |
Fix Released
|
Low
|
Laurynas Biveinis | |||
5.7 |
Fix Released
|
Low
|
Laurynas Biveinis |
Bug Description
On 5.6 trunk, seen on ASan build:
innodb.
Test ended at 2017-02-06 12:45:29
line
2017-02-06 20:45:29 26455 [Warning] InnoDB: Recovery skipped, --innodb-read-only set!
2017-02-06 20:45:29 26455 [ERROR] InnoDB: We scanned the log up to 0. A checkpoint was at 1632026 and the maximum LSN on a database page was 0. It is possible that the database is now corrupt!
2017-02-06 20:45:29 7fb1ac7c7780 InnoDB: Error: page 5 log sequence number 1632036
^ Found warnings in /mnt/workspace/
ok
tags: | added: ci |
tags: | added: log-archiving xtradb |
tags: | removed: log-archiving |
InnoDB read only mode restart requires a preceding slow shutdown, which the current innodb. percona_ log_archive_ ro does not do. Another Percona testcase that does not do it is innodb. xtradb_ compressed_ columns_ read_only