diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2019-11-20 12:06:01 +0000 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2019-11-20 12:06:01 +0000 |
commit | a68e9d3318c6847436f81f83eb347b29f52d1bff (patch) | |
tree | 511a790297f7e771f8d73025b9a1f9b4a0586d71 /doc/administration/gitaly/praefect.md | |
parent | 7bc0aff0b4e15fce828621d7e0919d84368f3d2b (diff) | |
download | gitlab-ce-a68e9d3318c6847436f81f83eb347b29f52d1bff.tar.gz |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration/gitaly/praefect.md')
-rw-r--r-- | doc/administration/gitaly/praefect.md | 8 |
1 files changed, 3 insertions, 5 deletions
diff --git a/doc/administration/gitaly/praefect.md b/doc/administration/gitaly/praefect.md index 667fd48a91c..1c01f3cebd5 100644 --- a/doc/administration/gitaly/praefect.md +++ b/doc/administration/gitaly/praefect.md @@ -20,11 +20,10 @@ for updates and roadmap. ### Architecture -For this document, the following network topology is assumed: +The most common architecture for Praefect is simplified in the diagram below: ```mermaid graph TB - GitLab --> Gitaly; GitLab --> Praefect; Praefect --> Gitaly-1; Praefect --> Gitaly-2; @@ -32,9 +31,8 @@ graph TB ``` Where `GitLab` is the collection of clients that can request Git operations. -`Gitaly` is a Gitaly server before using Praefect. The Praefect node has three -storage nodes attached. Praefect itself doesn't store data, but connects to -three Gitaly nodes, `Praefect-Gitaly-1`, `Praefect-Gitaly-2`, and `Praefect-Gitaly-3`. +The Praefect node has threestorage nodes attached. Praefect itself doesn't +store data, but connects to three Gitaly nodes, `Gitaly-1`, `Gitaly-2`, and `Gitaly-3`. Praefect may be enabled on its own node or can be run on the GitLab server. In the example below we will use a separate server, but the optimal configuration |