INFORMATION_SCHEMA.INNODB_CHANGED_PAGES queries needlessly read potentially incomplete bitmap data past the query range
Bug #1625466 reported by
Laurynas Biveinis
This bug affects 1 person
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
This is different from bug 1620532.
On PS 5.6 trunk:
innodb.
Test ended at 2016-09-15 14:14:47
CURRENT_TEST: innodb.
mysqltest: At line 177: query 'reap' failed: 1012: Can't read record in system table
...
2016-09-15 17:14:47 22420 [ERROR] InnoDB: simulating bitmap write error in log_online_
2016-09-15 17:14:47 22420 [Warning] InnoDB: changed page bitmap file './ib_modified_
...
tags: | added: bitmap ci |
To post a comment you must log in.
This is caused by the INNODB_ CHANGED_ PAGES iterator reading one more page past the query range and then stopping the iteration by comparing its start LSN to range end LSN. If that page happens to be corrupted, it would needlessly fail the query with a "Can't find a system record".