Spurious messages: Got error -1 when reading table ...
Bug #987136 reported by
Seppo Jaakola
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| MySQL patches by Codership |
New
|
Low
|
Unassigned | |||
| 5.5 |
New
|
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_
How to repeat:
1. Configure with innodb_
2. use nodes and run conflicting multi-master load
3. use queries with sub selects
Revision history for this message
| Seppo Jaakola (seppo-jaakola) wrote | #1 |
| 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 |
Revision history for this message
| Raghavendra D Prabhu (raghavendra-prabhu) wrote | #2 |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #3 |
To post a comment you must log in.
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.