This is a discussion on MySQL replication fail over? within the MySQL forums, part of the Database Server Software category; --> Hello, A lot of resources teach about how to set up MySQL replication, how to use it ect. But ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello, A lot of resources teach about how to set up MySQL replication, how to use it ect. But not many of them teach how to fail over instead of incident, especially when master failed, how to promote slave into master - automatically or minimize the delay, data inconsistency etc. Are there any books/articles I should read for learning fail over techniques (especially common enterprise practices)? Thanks. |
| ||||
| On Nov 3, 6:04 am, howa <howac...@gmail.com> wrote: > Hello, > > A lot of resources teach about how to set up MySQL replication, how to > use it ect. > > But not many of them teach how to fail over instead of incident, > especially when master failed, how to promote slave into master - > automatically or minimize the delay, data inconsistency etc. > > Are there any books/articles I should read for learning fail over > techniques (especially common enterprise practices)? > > Thanks. This is something that MySQL provides products for, and I don't believe is available in the community version. See http://www.mysql.com/products/database/cluster/ for more information on what MySQL provides. The Cluster packages themselves provide fail-over capability. Aside from that, try checking out the free "Linux Heartbeat" at http://www.linux-ha.org/.. which provides availability monitoring and such. I'm not sure about any automated fail-over, though. Usually those are things companies make, that other companies pay a lot of money for. |
| Thread Tools | |
| Display Modes | |
|
|