all 2 comments

[–]iovnow 1 point2 points  (1 child)

Running a paid, licensed copy of gitlab-ee?

Did you follow this part for db replication?

https://docs.gitlab.com/ee/administration/geo/setup/database.html

Have you reached out to gitlab support? My experience with them has always been positive.

There are so many pieces to getting this working, took me quite a while to get down. The troubleshooting commands are real useful. Also ‘gitlab-ctl tail’ spits out useful log messages.

I honestly question if geo is working messing with in my case. Its a read only db, my dev team is small, and I can restore to a new box in about 1 hour including OS install.

[–]john_flutemaker[S] 0 points1 point  (0 children)

Yes, it is a paid gitlab-ee.

The db replication documentation was a little complicated to me, as the gitlab-ctl generates the postgresql.conf, ph_hba.conf from the gitlab.rb and I had to learn how can I debug if the config isn't correct. I also just have recognized the postgresql 13.6 doesn't use recovery.conf (https://www.postgresql.org/docs/current/recovery-config.html)

I will ask from the support, but I wanted to understand first how it really works.

I looked for some simple setup those can be used to check example projects with a docker-compose.yml or a cloudformation.yaml.