LSN rolls back by 10 on shutdown intermittently
Bug #1622868 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 | Status tracked in 5.7 | |||||
| 5.5 |
New
|
Undecided
|
Unassigned | |||
| 5.6 |
In Progress
|
Medium
|
Unassigned | |||
| 5.7 |
In Progress
|
Undecided
|
Unassigned | |||
Bug Description
On PS 5.6 trunk / upstream, extremely intermittently:
2016-08-30 16:38:10 18262 [Warning] InnoDB: The log sequence number in the ibdata files is higher than the log sequence number in the ib_logfiles! Are you sure you are using the right ib_logfiles to start up the database. Log sequence number in the ib_logfiles is 1625987, logsequence numbers stamped to ibdata file headers are between 1625997 and 1625997.
^ Found warnings in /mnt/workspace/
ok
| tags: | added: ci innodb upstream |
Revision history for this message
| Laurynas Biveinis (laurynas-biveinis) wrote | #1 |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #2 |
To post a comment you must log in.
innodb.innodb_mysql w3 [ fail ] Found warnings/errors in server log file!
Test ended at 2017-03-05 08:30:09
line
2017-03-05 16:29:04 20438 [Warning] InnoDB: The log sequence number in the ibdata files is higher than the log sequence number in the ib_logfiles! Are you sure you are using the right ib_logfiles to start up the database. Log sequence number in the ib_logfiles is 1631996, logsequence numbers stamped to ibdata file headers are between 1632006 and 1632006.
^ Found warnings in /mnt/workspace/
ok