GEO: pausing and resuming replication using external databases
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Release notes
Problem to solve
An ultimate customer is requesting the possibility to have the GEO pausing and resuming replication feature enabled to use it with external databases. Currently this option is limited only to GitLab managed databases, which limits its usability for large HA architectures.
Intended users
Developer, Dev Ops engineers, System administrators
User experience goal
The user should be able to configure GitLab to use external databases when setting up GEO pause and resume replication feature.
Proposal
Enable the possibility of customers to configure external databases for replication pausing and resuming.
Further details
This a case of study from an Ultimate customer (Internal)
Permissions and Security
Documentation
Availability & Testing
Available Tier
What does success look like, and how can we measure that?
Customers of GitLab ultimate are able to setup their external databases when using GEO replication features.
What is the type of buyer?
Is this a cross-stage feature?
Links / references
https://docs.gitlab.com/ee/administration/geo/#pausing-and-resuming-replication