Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • omnibus-gitlab omnibus-gitlab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 1,061
    • Issues 1,061
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 67
    • Merge requests 67
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • omnibus-gitlabomnibus-gitlab
  • Issues
  • #5628
Closed
Open
Issue created Sep 08, 2020 by Gabriel Mazetto@brodock🔴Developer

Allow configuring permanent replication slots in patroni

Patroni handles replication slots automatically when new nodes are added to the "cluster". This does not work when you are adding a standby cluster, as it lives in a different DCS. The only way to enable a persistent replication slot in that case is to manually create them or by defining a configuration variable in Patroni to create and keep that alive.

That configuration variable needs to be exposed in Omnibus.

Assignee
Assign to
Time tracking