Wrong initial value for srv_track_changed_pages

Bug #1203308 reported by Alexey Kopytov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Fix Released
Low
Laurynas Biveinis
5.1
Fix Released
Low
Laurynas Biveinis
5.5
Fix Released
Low
Laurynas Biveinis
5.6
Fix Released
Low
Laurynas Biveinis

Bug Description

srv_track_changed_pages is defined in srv0srv.c[c] as follows:

UNIV_INTERN my_bool srv_track_changed_pages = TRUE;

Which contradicts the corresponding server option's default value (FALSE). Since option parsing is performed before the changed pages tracking is initialized, it is changed from its initial value to FALSE on startup, so everything accidentally works as documented.

It only becomes a problem when XtraBackup is rebased on the newer PS versions. Since XtraBackup doesn't use the plugin options parsing facility (and thus ignores innodb_track_changed_pages and its default value), it uses the initial value defined srv0srv. As a result, XtraBackup recovery starts with page tracking enabled.

Related branches

tags: added: low-hanging-fruit
tags: added: bitmap xtradb
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.