ec2-consistent-snapshot

Don't stop mysql if temp tables exists

Reported by Steve Caldwell on 2011-07-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ec2-consistent-snapshot
Medium
Eric Hammond

Bug Description

We've been having trouble when running the script with the --mysql-stop command against a slave database. What happens is that the script will shutdown mysql while the slave has temporary tables in memory, the tables are lost, and then the slave will not start correctly on either the host machine or from the snapshot.

See:
http://dev.mysql.com/doc/refman/5.1/en/replication-features-temptables.html

A fix for this would be to have ec2-consistent-snapshot perform the procedure listed on that url, namely to stop the slave sql thread, check if any temp tables exist, and abandon if so. ec2-consistent-snapshot could retry multiple times, and then refuse to stop mysql if it can't get to a state without temp tables.

Eric Hammond (esh) wrote :

Thank you for submitting this report. I love the idea. If you or somebody on your team would like to submit a patch for this behavior, I will gladly review it for merging.

Changed in ec2-consistent-snapshot:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Eric Hammond (esh)
Steve Caldwell (scaldwell) wrote :

Eric: we'll work on that.

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

Other bug subscribers