jprdonnelly/docs
1
0
Fork 0
mirror of synced 2026-02-02 15:02:03 -05:00
Code Issues Projects Releases Wiki Activity

Merge pull request #11483 from astone2014/main

Browse Source 
Small grammar change on "About geo-replication" page
This commit is contained in:
Ramya Parimi
2021-11-04 10:34:33 -05:00
committed by GitHub
parent 35ae909ff4 9563df1493
commit 362f1dd7bd
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md
View File

@@ -22,7 +22,7 @@ Geo DNS, such as [Amazon's Route 53 service](http://docs.aws.amazon.com/Route53/
## Limitations
Writing requests to the replica requires sending the data to the primary and all replicas. This means that the performance of all writes are limited by the slowest replica, although new geo-replicas can seed the majority of their data from existing co-located geo-replicas, rather than from the primary. Geo-replication will not add capacity to a {% data variables.product.prodname_ghe_server %} instance or solve performance issues related to insufficient CPU or memory resources. If the primary appliance is offline, active replicas will be unable to serve any read or write requests.
Writing requests to the replica requires sending the data to the primary and all replicas. This means that the performance of all writes is limited by the slowest replica, although new geo-replicas can seed the majority of their data from existing co-located geo-replicas, rather than from the primary. Geo-replication will not add capacity to a {% data variables.product.prodname_ghe_server %} instance or solve performance issues related to insufficient CPU or memory resources. If the primary appliance is offline, active replicas will be unable to serve any read or write requests.
{% data reusables.enterprise_installation.replica-limit %}