Simple Deployment
Auto-installation with one command is supported. MogHA can start upon simple configurations.
Decoupled from Instances
Database instances are not bound with MogHA and their startup modes are the same.
Dual Modes
MogHA supports primary/standby deployment and also one primary and multiple standby nodes.
Why Is MogHA Still Needed Even If a Database Supports Primary/Standby?
We need to understand what is high availability. High availability can make a database provide uninterrupted services to ensure stable running of upper-layer services. That a database supports primary/standby deployment aims to prevent single point of failures, but it does not offer fault detection and automatic primary/standby switchover. Therefore, MogHA is needed. It provides a system for monitoring the instance status and the primary/standby status and triggering primary/standby failover once it detects a failure.
Functions and Characteristics
Failover
Detect faults in instances.
Detect faults in networks.
Detect faults in disks.
Instance Monitoring
Recognize the instance role.
Monitor the status of an instance.
Support CPU binding.
Split Brain
Detect split-brain faults.
Support independent decision-making.
Remove the split-brain instance.
Virtual IP Address
Support automatic drift.
Support automatic broadcast.
Support online check.
Hands-on Experience
Are you ready to get started with MogHA? We have prepared everything for you! If you have any question, you can view our docs, visit our community, or contact us.