Skip to content

Commit 362f1dd

Browse files
authored
Merge pull request #11483 from astone2014/main
Small grammar change on "About geo-replication" page
2 parents 35ae909 + 9563df1 commit 362f1dd

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Geo DNS, such as [Amazon's Route 53 service](http://docs.aws.amazon.com/Route53/
2222

2323
## Limitations
2424

25-
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.
25+
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.
2626

2727
{% data reusables.enterprise_installation.replica-limit %}
2828

0 commit comments

Comments
 (0)