Commit b589e758 authored by Achilleas Pipinellis's avatar Achilleas Pipinellis

Merge branch 'ebrinkman-master-patch-82776' into 'master'

Update Praefect Documentation

See merge request gitlab-org/gitlab!20409
parents efe51aa7 be466917
...@@ -20,11 +20,10 @@ for updates and roadmap. ...@@ -20,11 +20,10 @@ for updates and roadmap.
### Architecture ### Architecture
For this document, the following network topology is assumed: The most common architecture for Praefect is simplified in the diagram below:
```mermaid ```mermaid
graph TB graph TB
GitLab --> Gitaly;
GitLab --> Praefect; GitLab --> Praefect;
Praefect --> Gitaly-1; Praefect --> Gitaly-1;
Praefect --> Gitaly-2; Praefect --> Gitaly-2;
...@@ -32,9 +31,8 @@ graph TB ...@@ -32,9 +31,8 @@ graph TB
``` ```
Where `GitLab` is the collection of clients that can request Git operations. 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 The Praefect node has threestorage nodes attached. Praefect itself doesn't
storage nodes attached. Praefect itself doesn't store data, but connects to store data, but connects to three Gitaly nodes, `Gitaly-1`, `Gitaly-2`, and `Gitaly-3`.
three Gitaly nodes, `Praefect-Gitaly-1`, `Praefect-Gitaly-2`, and `Praefect-Gitaly-3`.
Praefect may be enabled on its own node or can be run on the GitLab server. 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 In the example below we will use a separate server, but the optimal configuration
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment