Crash in 5.5.15-55
Bug #856611 reported by
Dan Rogers
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MySQL Server |
Unknown
|
Unknown
|
|||
| Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
High
|
Unassigned | ||
| 5.1 |
Won't Fix
|
High
|
Unassigned | ||
| 5.5 |
Fix Released
|
High
|
Unassigned | ||
Bug Description
We have a Percona Server 5.5.15-55 install with a master (db01) and two slaves (db03 & db04), running replication between the servers. db03 is also the master for db01 for cases where we need to bring db01 down for maintenance.
Yesterday, we we had a near-simultaneous crash of MySQL on all three servers, leading me to believe it was caused by a query that propagated between them.
I've attached the relevant log entries from the MySQL log. Please let me know if I can provide any further information.
Thanks.
Dan.
Revision history for this message
| Dan Rogers (drogers-l) wrote | #1 |
Revision history for this message
| Alexey Kopytov (akopytov) wrote | #2 |
| Changed in percona-server: | |
| status: | New → Confirmed |
Revision history for this message
| Dan Rogers (drogers-l) wrote | #3 |
| Changed in percona-server: | |
| importance: | Undecided → High |
| status: | Confirmed → Triaged |
Revision history for this message
| Alexey Kopytov (akopytov) wrote | #4 |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #5 |
To post a comment you must log in.
The crash is a result of trying to create a temporary InnoDB table on tmpfs. The reason is that async I/O is not supported on the tmpfs filesystem, see http://
A workaround is to either set innodb_