1cd5e13652
Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com> Co-authored-by: Felicity Chapman <felicitymay@github.com> Co-authored-by: Sarah Schneider <sarahs@github.com>
2.6 KiB
title, intro, redirect_from, versions, type, topics, shortTitle
| title | intro | redirect_from | versions | type | topics | shortTitle | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Initiating a failover to your replica cluster | If your {% data variables.product.prodname_ghe_server %} cluster fails, you can fail over to the replica. |
|
|
how_to |
|
Initiate a failover to replica |
About failover to your replica cluster
If the data center for your active cluster experiences a failure and you've configured high availability, you can fail over to your replica cluster.
Failing over to your replica cluster promotes it to be your new active cluster, and decouples the new active cluster from the old active cluster. The nodes in your old active cluster are placed in maintenance mode if they are in a healthy enough state for this operation to be performed.
After failover, you will have two standalone clusters without high availability configured. You can reconfigure replication from the new active cluster. For more information, see AUTOTITLE.
Prerequisites
To fail over to replica nodes, you must have configured high availability replication for your cluster. For more information, see AUTOTITLE.
Initiating a failover to your replica cluster
-
SSH into the primary MySQL node in the replica cluster. For more information, see AUTOTITLE.
-
To begin the failover to the secondary cluster and configure the nodes to respond to requests, run the following command.
ghe-cluster-failover
{% data reusables.enterprise_clustering.configuration-finished %}
- Update the DNS record to point to the IP address of the load balancer for your replica cluster. After the TTL period expires, requests will be directed to the replica cluster.
After {% data variables.product.prodname_ghe_server %} returns you to the prompt and your DNS updates propagate, you've finished failing over. Users can access {% data variables.product.prodname_ghe_server %} using the usual hostname for your cluster.