Comments (4)
And of course I meant Pacemaker ;)
Original comment by [email protected]
on 20 Sep 2012 at 12:36
from mysql-master-ha.
If you code virtual IP failover logic inside a custom script and call it from
MHA by "master_ip_failover_script" parameter
(http://code.google.com/p/mysql-master-ha/wiki/Parameters#master_ip_failover_scr
ipt), you can do virual IP failover without using clustering software. I hear
some users/customers have written such logic.
> The document on
http://code.google.com/p/mysql-master-ha/wiki/Using_With_Clustering_Software
describes how to do that with a simple two node scenario but that wouldn't work
for me...
I think that works in your case as well. By managing master and slave1 via
Pacemaker, when master goes down you can do failover to slave1. MHA has
parameters so that it always try to failover to slave1 (See
http://code.google.com/p/mysql-master-ha/wiki/Parameters#candidate_master and
http://code.google.com/p/mysql-master-ha/wiki/Parameters#no_master). If both
master and slave1 go down at the same time, failover won't work, but in such
serious cases automated failover should not happen.
Original comment by [email protected]
on 21 Sep 2012 at 1:42
from mysql-master-ha.
If I don't use clustering software I may end up with two servers having the
same IP address.
This can happen if someone pulls out the network cable from the master (by
accident), MHA will promote a different master and assign it the same IP.
With clustering the old master will detect that there is a new server in the
cluster and it will never reuse the virtual IP.
The thing is I have more than just one slave and I don't want to fail over to a
specific slave but to a slave which has the latest relay log events and this
can't be defined with priorities but has to be determined dynamically.
With the setup described in
http://code.google.com/p/mysql-master-ha/wiki/Using_With_Clustering_Software is
states specifically which server would be a preferred master and which will be
ignored.
I want this to work with masterha_manager which will decide which slave to fail
over to...
Original comment by [email protected]
on 24 Sep 2012 at 10:03
from mysql-master-ha.
> This can happen if someone pulls out the network cable from the master (by
accident), MHA will promote a different master and assign it the same IP.
In such scenario, I highly recommend to force shutdown the original master, or
doing nothing (do not start failover). Commands to force shutdown depend on
H/W. Some samples are under samples/scripts/ from MHA Manager tarball. By
shutting down the original master, you can avoid having two same IP address at
least.
I understand your request to promote the latest slave, not a specific slave. In
that case, implementing forcing shutdown logic and activating IP address logic
in MHA failover script
(http://code.google.com/p/mysql-master-ha/wiki/Parameters#master_ip_failover_scr
ipt) makes more sense to me. As described above, forcing shutdown logic highly
depends on H/W. Activating IP address logic can be borrowed from clustering
software.
Original comment by [email protected]
on 25 Sep 2012 at 10:37
from mysql-master-ha.
Related Issues (20)
- Not support for detecting poor perfomance masters HOT 1
- Manual switching | alive Old master does't become new slave HOT 3
- MHA automatic failover stop when I shutdown Master machine
- If Active Master goes Down, Slave running MHA manager can become Master?. HOT 2
- MHA IP failover / firewall issues
- got the error during the failover test "Applying all logs succeeded. But starting slave failed" HOT 3
- masterha_check_repl skips all slave checks on MySQL 5.6 with GTID enabled HOT 3
- Do mysql master failover only when there are more than one slaves HOT 3
- Maunal purge_relay_logs crash my replication HOT 2
- Failover aborts due to 1053 - Query partially completed on the master HOT 2
- masterha_manager can not start on 3306 ,but 3313 ok
- Does mysql-master-ha work if I already have traditional mysql replication running? HOT 1
- masterha_check_repl says ssh config failed, BUT masterha_check_ssh was okay HOT 1
- alert-only mode instead of failover
- Master Failover completed successfully. Error Establishing Database Connection. HOT 2
- Documentation not available HOT 1
- masterha_check_repl crashing HOT 2
- MHA Scalability HOT 1
- mysql innodb locks during checks on slaves
- Plaintext password in output HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mysql-master-ha.