pt-fk-error-logger displays same Foreign key error repeatedly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Toolkit moved to https://jira.percona.com/projects/PT |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
pt-fk-error-logger reports the same FK Error message again and again.
perl pt-fk-error-logger h=sedodbdevha1.
percona-
MySQL 5.1
Output -
160616 8:53:13 Transaction:
TRANSACTION 0 174698243, ACTIVE 0 sec, process no 26029, OS thread id 139991371470592 inserting, thread declared inside InnoDB 500
mysql tables in use 2, locked 2
3 lock struct(s), heap size 368, 1 row lock(s), undo log entries 1
MySQL thread id 47407, query id 1241485 172.29.14.249 sdbrw update
insert into Table_Commentat
,2342334,123)
Foreign key constraint fails for table `dbsedo`
,
CONSTRAINT `Table_
Trying to add in child table, in index `idxTableCommen
DATA TUPLE: 2 fields;
0: len 3; hex ffffff; asc ;; 1: len 3; hex 000edb; asc ;;
But in parent table `dbsedo`.`Table`, in index `PRIMARY`,
the closest match we can find is record:
PHYSICAL RECORD: n_fields 23; compact format; info bits 0
0: len 3; hex 029ea7; asc ;; 1: len 6; hex 000009c71b45; asc E;; 2: len 7; hex 00000040022f9e; asc @ / ;; 3: SQL NULL; 4: len 1; hex 01; asc ;; 5: len 4; hex 002205f1; asc " ;; 6: len 3; hex 000003; asc ;; 7: len 19; hex 66656e737465727
160616 8:53:13 Transaction:
TRANSACTION 0 174698243, ACTIVE 0 sec, process no 26029, OS thread id 139991371470592 inserting, thread declared inside InnoDB 500
mysql tables in use 2, locked 2
3 lock struct(s), heap size 368, 1 row lock(s), undo log entries 1
MySQL thread id 47407, query id 1241485 172.29.14.249 sdbrw update
insert into Table_Commentat
,2342334,123)
Foreign key constraint fails for table `dbsedo`
,
CONSTRAINT `Table_
Trying to add in child table, in index `idxTableCommen
DATA TUPLE: 2 fields;
0: len 3; hex ffffff; asc ;; 1: len 3; hex 000edb; asc ;;
But in parent table `dbsedo`.`Table`, in index `PRIMARY`,
the closest match we can find is record:
PHYSICAL RECORD: n_fields 23; compact format; info bits 0
0: len 3; hex 029ea7; asc ;; 1: len 6; hex 000009c71b45; asc E;; 2: len 7; hex 00000040022f9e; asc @ / ;; 3: SQL NULL; 4: len 1; hex 01; asc ;; 5: len 4; hex 002205f1; asc " ;; 6: len 3; hex 000003; asc ;; 7: len 19; hex 66656e737465727
Changed in percona-toolkit: | |
status: | New → Confirmed |
tags: | added: pt121 |
Thank you for the report.
Verified as described with versions 2.2.20 and 3.0.2.
To repeat:
- Create 2 tables, parent and child
- Produce any FK error, so it stays in SHOW ENGINE INNODB STATUS
- Do not do any other job on the server
- Wait at least 15 seconds after the tool prints the error first time and you will see it will print it again and again
This behavior is different from the documented at https:/ /www.percona. com/doc/ percona- toolkit/ 3.0/pt- fk-error- logger. html: " Foreign key errors are uniquely identified by their timestamp. Only new (more recent) errors are printed or saved."