Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
gitaly gitaly
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 676
    • Issues 676
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 36
    • Merge requests 36
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • gitalygitaly
  • Issues
  • #3334

Closed
Open
Created Dec 02, 2020 by Pavlo Strokov@8bitlifeMaintainer

Gitaly HA Distributed Reads

Release Notes

In a highly available Gitaly cluster you want to ensure the highest possible levels of read performance. Additionally, you want to minimize any potential impact that one repository can have to other repositories in the same cluster. With the introduction of distributed git reads to the HA Gitaly Cluster, you're now able to read from any node in the cluster that is currently up to date. This is especially impactful for very busy repositories, especially those with numerous concurrent CI/CD pipelines running, all of which are performing reads.

Documentation Link

Problem Statement

This issue created in order to track progress of rolling out a reads distribution feature.
Currently it is accessible behind a feature flag and should be enabled by default.

Edited Jan 12, 2021 by Mark Wood
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
13.8
Milestone
13.8 (Past due)
Assign milestone
Time tracking