Opened 8 years ago

Last modified 7 years ago

#152 new enhancement

hotter MySQL failover

Reported by: geofft Owned by:
Priority: normal Milestone:
Component: sql Keywords:
Cc:

Description

If the primary dies, it currently takes manual effort to get the secondary to start calling itself sql.mit.edu. 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.

Change History (2)

comment:1 Changed 8 years ago by quentin

We already have SQL configured to not need any of that dance. All you need to do is unbind the IP on the old server (if necessary), and bind it on the new server.

comment:2 Changed 7 years ago by ezyang

  • Type changed from defect to enhancement
Note: See TracTickets for help on using tickets.