How does Cluster Manager work in MySQL Cluster?
A: MySQL Cluster Manager is able to monitor cluster health at both an Operating System and per-process level by automatically polling each node in the cluster. It can detect if a process or server host is alive, dead or has hung, allowing for faster problem detection, resolution and recovery.
Can a MySQL Cluster be used for disaster recovery?
A: Yes, as long as your network has the characteristics discussed here. MySQL Cluster has long offered Geographic Replication, distributing clusters to remote data centers to reduce the affects of geographic latency by pushing data closer to the user, as well as providing a capability for disaster recovery.
How many hosts do I need for MySQL Cluster?
A: For evaluation and development purposes, you can run all nodes on a single host. For full redundancy and fault tolerance, you would need a minimum 6 x physical hosts: Many users co-locate the Management and Application nodes which reduces the number of nodes to four.
How does geographic replication work in MySQL Cluster?
MySQL Cluster has long offered Geographic Replication, distributing clusters to remote data centers to reduce the affects of geographic latency by pushing data closer to the user, as well as providing a capability for disaster recovery. Geographic replication is asynchronous and can be implemented as an Active / Active or Active / Passive cluster.
What to do when MySQL Cluster goes offline?
If your cluster suffers from a complete outage or you want to start the cluster after a clean shutdown, you can ensure it is reconfigured correctly using dba.rebootClusterFromCompleteOutage () function. It simply brings a cluster back ONLINE when all members are OFFLINE.
How does MySQL InnoDB cluster connect to the cluster?
In the first part of this blog, we covered a deployment walkthrough of MySQL InnoDB Cluster with an example on how the applications can connect to the cluster via a dedicated read/write port.