id	summary	reporter	owner	description	type	status	priority	milestone	component	resolution	keywords	cc
152	hotter MySQL failover	geofft		If the primary dies, it currently takes manual effort to get the secondary to start calling itself sql.mit.edu. [http://dev.mysql.com/doc/refman/5.1/en/replication-solutions-switch.html talks about the process]. It would be good if at least a little bit of this (like binding sql.mit.edu) were automated, even if we continued to page maintainers to make sure nothing terribly unexpected was happening and to clean up the crash of the former primary and try to get it back on its feet. Since we only have two machines at the moment, this is a bit easier since there are no additional secondaries that need to be informed of what's going on.	enhancement	new	normal		sql