min_flushed_lsn in not updated after log size changing

Bug #1172591 reported by Vlad Lesin
6
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.

Tags: xtradb

Related branches

Vlad Lesin (vlad-lesin)
description: updated
Changed in percona-server:
assignee: nobody → Vlad Lesin (vlad-lesin)
tags: added: 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-1358

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.