Spurious messages: Got error -1 when reading table ...

Bug #987136 reported by Seppo Jaakola on 2012-04-23
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Low
Unassigned
5.5
Low
Unassigned
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
Status tracked in 5.6
5.5
Confirmed
Medium
Unassigned
5.6
Confirmed
Medium
Unassigned

Bug Description

Spurious messages of pattern: Got error -1 when reading table ... can appear in error log.

This can happen especially when running with configuration where innodb_locks_unsafe_for_binlog is not set

How to repeat:
1. Configure with innodb_locks_unsafe_for_binlog=0
2. use nodes and run conflicting multi-master load
3. use queries with sub selects

Seppo Jaakola (seppo-jaakola) wrote :

InnoDB error handler does not do a good job here. This accounts for DB_INTERRUPTED errors in InnoDB.
The fix should be to avoid printing these messages if BF abort caused the query interrupt.

Changed in codership-mysql:
importance: Undecided → Low
milestone: none → 5.5.22-23.6
Changed in codership-mysql:
milestone: 5.5.33-24.8 → none

Yes, the -1 is indeed due to BF aborts, currently I filter it out in RQG so that false positives are avoided. It would be better to fix this in mysqld itself.

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1036

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers