Geo: Improve HA install docs
What does this MR do?
Improves Geo HA docs.
- Adds caveat that we don't support PG HA in secondaries
- Suggest ensuring the secondary cluster works without Geo first
- Adds configuration to disable
geo_logcursor
on the PG read-replica node to prevent it from attempting to configure Rails if you don't have any Rails services explicitly enabled. Otherwise,reconfigure
could get blocked on things like erroring on migrating databases even though you never asked to rungeo_logcursor
on the PG node. - Adds suggestion to run backend Rails services on backend application nodes
Related issues
Author's checklist
-
Follow the Documentation Guidelines and Style Guide. -
If applicable, update the permissions table. -
Link docs to and from the higher-level index page, plus other related docs where helpful. -
Apply the documentation label.
Review checklist
All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.
1. Primary Reviewer
-
Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.
2. Technical Writer
-
Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.
3. Maintainer
-
Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review. -
Ensure a release milestone is set. -
If there has not been a technical writer review, create an issue for one using the Doc Review template.
Edited by 🤖 GitLab Bot 🤖