If Active Master goes Down, Slave running MHA manager can become Master?.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. I have 2 nodes (Master-Slave) pair ,Configured Multi-Master Replication with 
one Master with Read-only.
2. Installed MHA Node on Both Nodes (Master(M1)-Master(M2) ) and installed MHA 
Manager on Master (M2).
3. If Active Master (M1) goes down. does Master (M2) can become Active Master 
provided MHA Manager running on Master (M2).  

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?
MHA MANAGER version - mha4mysql-manager-0.56-0.el6.noarch
MHA NODE version - mha4mysql-node-0.56-0.el6.noarch
Mysql Version - 5.5.34 - community
RHEL -6


Please provide any additional information below.
 For High Avialability & Failover using MHA , As i am going to implement the setup in production Environment , please  suggest me accordingly.

Original issue reported on code.google.com by [email protected] on 25 Nov 2014 at 7:59

[GoogleCodeExporter]

MHA needs two or more slaves. This is because if you have only one master and 
one slave, most parts of the MHA roles (finding the most advanced slave, 
applying differential relay logs) are not needed so you don't need to use MHA.

If you have two or more slaves, slave running MHA manager can become master.

Original comment by [email protected] on 25 Nov 2014 at 8:49

[GoogleCodeExporter]

Thanks allot Yoshinor , please suggest me how can i achieve that task.

Original comment by [email protected] on 26 Nov 2014 at 6:43