Update PgBouncer Recommendation for HA in Documentation
What does this MR do?
Updates Scaling and High Availability docs with new best practice for PgBouncer setup with Omnibus.
New recommended setup is to deploy multiple PgBouncer nodes (one for each Postgres) with a manually setup internal load balancer (TCP) serving them. This is the recommendation for now as PgBouncer itself isn't HA but may get replaced in the future with a bigger solution.
Related issues
gitlab-org/quality/performance#118 (closed)
Author's checklist
-
Follow the Documentation Guidelines and Style Guide. -
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 and that you merge the equivalent EE MR before the CE MR if both exist. -
If there has not been a technical writer review, create an issue for one using the Doc Review template.
Edited by 🤖 GitLab Bot 🤖