Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not support for detecting poor perfomance masters #100

Open
GoogleCodeExporter opened this issue Jul 30, 2015 · 1 comment
Open

Not support for detecting poor perfomance masters #100

GoogleCodeExporter opened this issue Jul 30, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link
Contributor

Is this tool supports to detect poor performing master and then do fail-over. 
Instead of detecting dead-master.

Because, Frequently we are facing problem with Master performance degradation 
instead of completely dead

Original issue reported on code.google.com by [email protected] on 20 Nov 2014 at 1:07

@GoogleCodeExporter
Copy link
Contributor Author

MHA does not handle a master as dead, if the master is running, even though the 
master performance degrades. This is to prevent repeating failover and false 
alarm. For example, if there are bugs in application logic, failover won't fix 
the problem so starting failover does not make any sense.

If you want MHA to start promotion, shutdown the master instance (by an 
external script or manually). The script should be smart enough that it 
understands failover fixes the problem (i.e. hardware problem on the master 
server).

Original comment by [email protected] on 21 Nov 2014 at 9:10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant