min_flushed_lsn in not updated after log size changing
Bug #1172591 reported by
Vlad Lesin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Medium
|
Vlad Lesin | ||
5.1 |
Invalid
|
Undecided
|
Unassigned | ||
5.5 |
Invalid
|
Undecided
|
Unassigned | ||
5.6 |
Fix Released
|
Medium
|
Vlad Lesin |
Bug Description
If 5.6 server starts and log file size is changed the current lsn of new created log file is aligned up the log block size but min_flushed_lsn in data file remains untouched. So arhived logs are started with one lsn value buf data files contains the other flushed lsn value. That caused the error during archived logs applying.
Related branches
lp:~vlad-lesin/percona-server/5.6-xtrabackup-apply-logs-fixes
- Alexey Kopytov (community): Approve
- Laurynas Biveinis (community): Needs Information
-
Diff: 32 lines (+8/-2)2 files modifiedPercona-Server/mysql-test/suite/innodb/t/innodb-log-file-size.test (+1/-1)
Percona-Server/storage/innobase/srv/srv0start.cc (+7/-1)
description: | updated |
Changed in percona-server: | |
assignee: | nobody → Vlad Lesin (vlad-lesin) |
tags: | added: xtradb |
To post a comment you must log in.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/ /jira.percona. com/browse/ PS-1358