Percona server innodb errors - unable to purge a record

Hi,

I have an active+master master setup and currently going through upgrading the ‘slave’ server to percona 5.6.20. The active master is running 5.5.35.

After the upgrade i keep seeing the following InnoDB alerts in my logs:

Sep 12 07:22:31 ss-p-db13 mysqld: 2014-09-12 07:22:31 7ff5ec951700 InnoDB: unable to purge a record
Sep 12 07:22:31 ss-p-db13 mysqld: InnoDB: tuple DATA TUPLE: 2 fields;
Sep 12 07:22:31 ss-p-db13 mysqld: 0: len 8; hex 000180001016fd7b; asc {;;
Sep 12 07:22:31 ss-p-db13 mysqld: 1: len 8; hex 0001800010208521; asc !;;
Sep 12 07:22:31 ss-p-db13 mysqld: 
Sep 12 07:22:31 ss-p-db13 mysqld: InnoDB: record PHYSICAL RECORD: n_fields 2; compact format; info bits 0
Sep 12 07:22:31 ss-p-db13 mysqld: 0: len 8; hex 000180001016fd7b; asc {;;
Sep 12 07:22:31 ss-p-db13 mysqld: 1: len 8; hex 0001800010208521; asc !;;
Sep 12 07:22:31 ss-p-db13 mysqld: 
Sep 12 07:22:31 ss-p-db13 mysqld: space 97 offset 1479882 (590 records, index id 230)
Sep 12 07:22:31 ss-p-db13 mysqld: InnoDB: Submit a detailed bug report to http://bugs.mysql.com

Ive used the pt-online-schema-change tool to run a recreate on all tables [pt-online-schema-change --alter “ENGINE=InnoDB”] but im still seeing the alerts in the logs.

any advice would be appreciated.

thanks.

Hi,

It seems, you are getting this error due to deadlocks. Can you provide output of “SHOW ENGINE INNODB STATUS \G” ?
Also full error log will be also helpful to troubleshoot this issue.

Hi.

Thanks for taking a look at this post - much appreciated.

Ive attached the output of innodb status. Unable to paste in here due to character limit.

I have mysql error logging going to syslog and unfortunately the message i added to my first post is the only mysql alert i get in the logs.

Thanks.

innodb_status.txt (10.9 KB)