Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
3785d506
Commit
3785d506
authored
Aug 10, 2020
by
James Ramsay
Committed by
Evan Read
Aug 10, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Compare Gitaly clusters and sharding
parent
7425d7ad
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
32 additions
and
0 deletions
+32
-0
doc/administration/gitaly/img/cluster_example_v13_3.png
doc/administration/gitaly/img/cluster_example_v13_3.png
+0
-0
doc/administration/gitaly/img/shard_example_v13_3.png
doc/administration/gitaly/img/shard_example_v13_3.png
+0
-0
doc/administration/gitaly/praefect.md
doc/administration/gitaly/praefect.md
+32
-0
No files found.
doc/administration/gitaly/img/cluster_example_v13_3.png
0 → 100644
View file @
3785d506
27.1 KB
doc/administration/gitaly/img/shard_example_v13_3.png
0 → 100644
View file @
3785d506
14.5 KB
doc/administration/gitaly/praefect.md
View file @
3785d506
...
...
@@ -59,6 +59,38 @@ Follow the [HA Gitaly epic](https://gitlab.com/groups/gitlab-org/-/epics/1489)
for improvements including
[
horizontally distributing reads
](
https://gitlab.com/groups/gitlab-org/-/epics/2013
)
.
## Cluster or shard
Gitaly supports multiple models of scaling:
-
Clustering using Gitaly Cluster, where each repository is stored on multiple Gitaly nodes in the
cluster. Read requests are distributed between repository replicas and write requests are
broadcast to repository replicas.
-
Sharding using
[
repository storage paths
](
../repository_storage_paths.md
)
, where each repository
is stored on the assigned Gitaly node. All requests are routed to this node.
| Cluster | Shard |
|---|---|
| !
[
Cluster example
](
img/cluster_example_v13_3.png
)
| !
[
Shard example
](
img/shard_example_v13_3.png
)
|
Generally, Gitaly Cluster can replace sharded configurations, at the expense of additional storage
needed to store each repository on multiple Gitaly nodes. The benefit of using Gitaly Cluster over
sharding is:
-
Improved fault tolerance, because each Gitaly node has a copy of every repository.
-
Improved resource utilization, reducing the need for over-provisioning for shard-specific peak
loads, because read loads are distributed across replicas.
-
Manual rebalancing for performance is not required, because read loads are distributed across
replicas.
-
Simpler management, because all Gitaly nodes are identical.
Under some workloads, CPU and memory requirements may require a large fleet of Gitaly nodes and it
can be uneconomical to have one to one replication factor.
A hybrid approach can be used in these instances, where each shard is configured as a smaller
cluster.
[
Variable replication factor
](
https://gitlab.com/groups/gitlab-org/-/epics/3372
)
is planned
to provide greater flexibility for extremely large GitLab instances.
## Requirements for configuring a Gitaly Cluster
The minimum recommended configuration for a Gitaly Cluster requires:
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment