Add support for running GitLab Geo tracking database
1 unresolved thread
1 unresolved thread
Compare changes
Files
7+ 1
− 0
Do not update/delete: Banner broadcast message test data
Do not update/delete: Notification broadcast message test data
Secondary Geo Nodes will need a separate PostgreSQL tracking database to store progress. This MR depends on https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1197.
Currently this is only performed in the secondary (
gdk-geo
) instance, but I'm not sure if that's correct.How does the replica get set up?
@stanhu That's part of the next instruction, where they follow the replication guide.
Do we need to do this after replication setup?
Just noticed the intro for that guide is missing some information, opened https://gitlab.com/gitlab-org/gitlab-development-kit/merge_requests/285 to address.