MySQL crashes on ERROR: the age of the last checkpoint is..
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.1 |
Won't Fix
|
Undecided
|
Unassigned | |||
5.5 |
Triaged
|
High
|
Unassigned | |||
5.6 |
New
|
Undecided
|
Unassigned | |||
5.7 |
New
|
Undecided
|
Unassigned |
Bug Description
I have a server running Debian 6 (Squeeze) and Percona 5.5.
Logs indicate that for a while, there's been a warning that:
150202 22:19:18 InnoDB: ERROR: the age of the last checkpoint is 9448357,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
I am aware of what this means and that the innodb_
But since the upgrade to 5.5.41-
150202 22:19:18 InnoDB: Assertion failure in thread 1420909424 in file sync0rw.c line 569
InnoDB: Failing assertion: !lock->recursive
InnoDB: We intentionally generate a memory trap.
A full output of the log is attached (from the last checkpoint error, and onward). The corruption appeared to fix itself on this occasion (without anyone even noticing), but the next day it occurred again and we ended up with a totally corrupt database system after this. All I know is that I've not seen MySQL fatally crash on something like the checkpoint alert before. So unsure if it's a regression in the latest Percona 5.5, which we'd upgrade to a few days before.
System is 3.18.3-
no longer affects: | percona-server/5.7 |
This error has occurred again for us today despite having made the innodb_ log_buffer_ size change. The error just appears out of the blue in the log (attached).
I have found it occurring on other servers also only since running 5.5.41- rel37.0- 727.squeeze