diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-05-30 12:09:22 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-05-30 12:09:22 +0300 |
| commit | ef144889c1bb80372e25f38fc89c7832ce84417a (patch) | |
| tree | 54fa644c7be78fa1a562ca5f97b7f295647e1ce1 /doc/user | |
| parent | 286bddcf3c62ca6fc499e1d5b6e678c0866fecc4 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user')
| -rw-r--r-- | doc/user/gitlab_com/index.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/user/gitlab_com/index.md b/doc/user/gitlab_com/index.md index fae45e4b2d3..2fa77878cb0 100644 --- a/doc/user/gitlab_com/index.md +++ b/doc/user/gitlab_com/index.md @@ -438,6 +438,12 @@ See [non-configurable limits](../../security/rate_limits.md#non-configurable-lim for information on rate limits that are not configurable, and therefore also used on GitLab.com. +## GitLab.com-specific Gitaly RPC concurrency limits + +Per-repository Gitaly RPC concurrency and queuing limits are configured for different types of Git operations such as `git clone`. When these limits are exceeded, a `fatal: remote error: GitLab is currently unable to handle this request due to load` message is returned to the client. + +For administrator documentation, see [limit RPC concurrency](../../administration/gitaly/configure_gitaly.md#limit-rpc-concurrency). + ## GitLab.com logging We use [Fluentd](https://gitlab.com/gitlab-com/runbooks/tree/master/logging/doc#fluentd) |