Gitaly timeouts

Gitaly timeouts are configurable. The timeouts can be configured to make sure that long-running Gitaly calls don’t needlessly take up resources.

To access Gitaly timeout settings:

  1. On the left sidebar, select Search or go to.
  2. Select Admin Area.
  3. Select Settings > Preferences.
  4. Expand the Gitaly timeouts section.

Available timeouts

The following timeouts are available.

Default55 secondsTimeout for most Gitaly calls (not enforced for git fetch and push operations, or Sidekiq jobs). For example, checking if a repository exists on disk. Makes sure that Gitaly calls made within a web request cannot exceed the entire request timeout. It should be shorter than the worker timeout that can be configured for Puma. If a Gitaly call timeout exceeds the worker timeout, the remaining time from the worker timeout is used to avoid having to terminate the worker.
Fast10 secondsTimeout for fast Gitaly operations used within requests, sometimes multiple times. For example, checking if a repository exists on disk. If fast operations exceed this threshold, there may be a problem with a storage shard. Failing fast can help maintain the stability of the GitLab instance.
Medium30 secondsTimeout for Gitaly operations that should be fast (possibly within requests) but preferably not used multiple times within a request. For example, loading blobs. Timeout that should be set between Default and Fast.