INFORMATION_SCHEMA.INNODB_CHANGED_PAGES queries needlessly read potentially incomplete bitmap data past the query range

[Laurynas Biveinis]

This is different from bug 1620532.

On PS 5.6 trunk:

innodb.percona_changed_page_bmp_debug w1 [ fail ]
        Test ended at 2016-09-15 14:14:47

CURRENT_TEST: innodb.percona_changed_page_bmp_debug
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_write_bitmap_page
2016-09-15 17:14:47 22420 [Warning] InnoDB: changed page bitmap file './ib_modified_log_2_8608342.xdb' does not contain a complete run at the end.
...

[Laurynas Biveinis (laurynas-biveinis)]

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".

[Laurynas Biveinis (laurynas-biveinis)]

     https://github.com/percona/percona-server/pull/1260
     https://github.com/percona/percona-server/pull/1261

[Laurynas Biveinis (laurynas-biveinis)]

Seen on 5.5 too

[Laurynas Biveinis (laurynas-biveinis)]

https://github.com/percona/percona-server/pull/1565/

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1744