Skip to content

repo sync #22569

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Dec 9, 2022
Merged

repo sync #22569

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e7dd965
Adding a line to indicate warnings and errors when primary server is …
leiyu88 Dec 9, 2022
828b1a7
Merge branch 'main' into repo-sync
Octomerger Dec 9, 2022
2e1d288
Merge pull request #33385 from github/repo-sync
Octomerger Dec 9, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions ...onfiguring-high-availability/initiating-a-failover-to-your-replica-appliance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,13 @@ The time required to failover depends on how long it takes to manually promote t
```shell
$ ghe-repl-promote
```

{% note %}

**Note:** If the primary node is unavailable, warnings and timeouts may occur but can be ignored.

{% endnote %}

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.
6. Notify users that they can resume normal operations.
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)."
Expand Down