Skip to content

Commit 75b0d60

Browse files
authored
Merge pull request #22569 from github/repo-sync
repo sync
2 parents 361d806 + 2e1d288 commit 75b0d60

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -47,6 +47,13 @@ The time required to failover depends on how long it takes to manually promote t
4747
```shell
4848
$ ghe-repl-promote
4949
```
50+
51+
{% note %}
52+
53+
**Note:** If the primary node is unavailable, warnings and timeouts may occur but can be ignored.
54+
55+
{% endnote %}
56+
5057
5. Update the DNS record to point to the IP address of the replica. Traffic is directed to the replica after the TTL period elapses. If you are using a load balancer, ensure it is configured to send traffic to the replica.
5158
6. Notify users that they can resume normal operations.
5259
7. If desired, set up replication from the new primary to existing appliances and the previous primary. For more information, see "[About high availability configuration](/enterprise/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)."

0 commit comments

Comments
 (0)