Closed GoogleCodeExporter closed 8 years ago
This is an expected behavior. MHA checks all configured instances' status in
3.1 and if an elected new master is down after that MHA does not retry to
promote other slave anymore. MHA master promotion is an automated process so
your test situation is very rare case, and retrying to promote other slave does
not solve the problem entirely (what if the newly elected slave is down after
elected?). So stopping failover with error is fine I guess.
Original comment by Yoshinor...@gmail.com
on 7 Dec 2012 at 6:22
Thanks for the clarification.
Original comment by andrea.c...@gmail.com
on 10 Dec 2012 at 11:52
Original comment by Yoshinor...@gmail.com
on 12 Dec 2012 at 8:40
Original issue reported on code.google.com by
andrea.c...@gmail.com
on 7 Dec 2012 at 5:26