diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-02-20 12:09:13 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-02-20 12:09:13 +0300 |
| commit | 1ac794623a8be5dee111716a44dd04ff708f3541 (patch) | |
| tree | 6c18f9fbe0bd9978bd3e8d9b083d3a0ca180686e /doc/administration/geo | |
| parent | 5247fe0bef72fa922841a79d5dbefb47d95112fa (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration/geo')
| -rw-r--r-- | doc/administration/geo/replication/index.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/administration/geo/replication/index.md b/doc/administration/geo/replication/index.md index e3699f1544b..4eaf6a88575 100644 --- a/doc/administration/geo/replication/index.md +++ b/doc/administration/geo/replication/index.md @@ -30,7 +30,7 @@ Implementing Geo provides the following benefits: - Reduce from minutes to seconds the time taken for your distributed developers to clone and fetch large repositories and projects. - Enable all of your developers to contribute ideas and work in parallel, no matter where they are. -- Balance the load between your **primary** and **secondary** nodes, or offload your automated tests to a **secondary** node. +- Balance the read-only load between your **primary** and **secondary** nodes. In addition, it: @@ -249,6 +249,7 @@ This list of limitations only reflects the latest version of GitLab. If you are - [Selective synchronization](configuration.md#selective-synchronization) applies only to files and repositories. Other datasets are replicated to the **secondary** node in full, making it inappropriate for use as an access control mechanism. - Object pools for forked project deduplication work only on the **primary** node, and are duplicated on the **secondary** node. - [External merge request diffs](../../merge_request_diffs.md) will not be replicated if they are on-disk, and viewing merge requests will fail. However, external MR diffs in object storage **are** supported. The default configuration (in-database) does work. +- GitLab Runners cannot register with a **secondary** node. Support for this is [planned for the future](https://gitlab.com/gitlab-org/gitlab/issues/3294). ### Limitations on replication/verification |