Geo: Update Geo HA documentation
We need to update and clarify the Geo HA documentation. This has led to some confusion and customer issues.
It may be helpful to break out the settings a little more granular to help ensure users have the correct settings on each node. In one case, the customer had 4 front-end nodes each running a tracking database as well as a dedicated node running a tracking database.
We should also clarify that the gitlab.rb
files on the application nodes in each cluster need to be the same. For example, all frontend application nodes in the primary cluster need to have the same primary-specific configuration and all frontend application nodes in the secondary cluster need to have the same secondary-specific configuration.
Do we want to use the Omnibus GitLab High Availability Roles as opposed to geo_primary_role['enable']
and geo_secondary_role['enable']
?
We should also add a note about setting uid
and gid
to match across all nodes in the cluster to avoid permission issues.
~Geo ~Documentation customer
@mkozono @rnienaber @akaemmerle @harishsr @davinwalker
Customer tickets: https://gitlab.zendesk.com/agent/tickets/103114 and https://gitlab.zendesk.com/agent/tickets/102822 (internal use)