Log tracking is incompatible with innodb_force_recovery=6
Bug #1083596 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 |
Fix Released
|
Medium
|
Laurynas Biveinis | ||
| 5.1 |
Fix Released
|
Medium
|
Laurynas Biveinis | ||
| 5.5 |
Fix Released
|
Medium
|
Laurynas Biveinis | ||
Bug Description
--innodb_
InnoDB: The user has set SRV_FORCE_
InnoDB: Skipping log redo
InnoDB: Error: last tracked LSN is in future. This can be caused by mismatched bitmap files.
And the server quits. The fix is to skip log tracking initialization on forced recovery.
Related branches
lp:~laurynas-biveinis/percona-server/BT-16274-bug1083596-5.1
- Stewart Smith (community): Approve
-
Diff: 83 lines (+42/-2)4 files modifiedPercona-Server/mysql-test/suite/innodb_plugin/r/percona_changed_page_bmp.result (+7/-0)
Percona-Server/mysql-test/suite/innodb_plugin/t/percona_changed_page_bmp.test (+26/-0)
Percona-Server/storage/innodb_plugin/log/log0online.c (+4/-2)
Percona-Server/storage/innodb_plugin/srv/srv0start.c (+5/-0)
lp:~laurynas-biveinis/percona-server/BT-16274-bug1083596-5.5
- Stewart Smith (community): Approve
-
Diff: 83 lines (+42/-2)4 files modifiedPercona-Server/mysql-test/suite/innodb/r/percona_changed_page_bmp.result (+7/-0)
Percona-Server/mysql-test/suite/innodb/t/percona_changed_page_bmp.test (+26/-0)
Percona-Server/storage/innobase/log/log0online.c (+4/-2)
Percona-Server/storage/innobase/srv/srv0start.c (+5/-0)
| description: | updated |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #1 |
To post a comment you must log in.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/