Skip to content

GitLab Next

    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Menu
    Projects Groups Snippets
  • Get a free trial
  • Sign up
  • Login
  • Sign in / Register
  • gitaly gitaly
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 537
    • Issues 537
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 54
    • Merge requests 54
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • gitalygitaly
  • Issues
  • #3398
Closed
Open
Created Jan 05, 2021 by Grant Young@grantyoungDeveloper

Distributed Read Cache direct database connection doesn't work with Omnibus HA Postgres setup

Similar to #3356 (closed) there's another potential single point of failure with the in-memory cache for reads distribution added recently.

The cache needs a direct connection to Postgres and this is where it can fail. If the Postgres database goes down for any reason then this feature will stop working that in turn will impact performance heavily. Solutions for Postgres failover elsewhere in the product aren't available as they are all pretty much based on a PgBouncer + Consul setup, which can't be used here as PgBouncer doesn't support LISTEN operations.

As such I think solutions should be explored for this as I fear Distributed Reads failing is something that may tend to be missed more as nothing will break outright.

cc @8bitlife

Edited Jan 21, 2021 by Grant Young
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking