From cf6af48a22bffa33e6ccc705da7c00846379b928 Mon Sep 17 00:00:00 2001 From: Grant Young Date: Thu, 16 Dec 2021 12:27:55 +0000 Subject: [PATCH 1/2] Add note in 3k modifications section about DB LB --- doc/administration/reference_architectures/3k_users.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/administration/reference_architectures/3k_users.md b/doc/administration/reference_architectures/3k_users.md index a16c95befc2090..eb77f1bc8e53d2 100644 --- a/doc/administration/reference_architectures/3k_users.md +++ b/doc/administration/reference_architectures/3k_users.md @@ -2145,7 +2145,7 @@ but with smaller performance requirements, several modifications can be consider - Lowering node specs: Depending on your user count, you can lower all suggested node specs as desired. However, it's recommended that you don't go lower than the [general requirements](../../install/requirements.md). - Combining select nodes: Some nodes can be combined to reduce complexity at the cost of some performance: - GitLab Rails and Sidekiq: Sidekiq nodes can be removed and the component instead enabled on the GitLab Rails nodes. - - PostgreSQL and PgBouncer: PgBouncer nodes can be removed and the component instead enabled on PostgreSQL with the Internal Load Balancer pointing to them instead. + - PostgreSQL and PgBouncer: PgBouncer nodes could be removed and the component instead enabled on PostgreSQL with the Internal Load Balancer pointing to them instead. However please note to enable [Database Load Balancing](../postgresql/database_load_balancing.md) a separate PgBouncer array will still be required. - Reducing the node counts: Some node types do not need consensus and can run with fewer nodes (but more than one for redundancy). This will also lead to reduced performance. - GitLab Rails and Sidekiq: Stateless services don't have a minimum node count. Two are enough for redundancy. - Gitaly and Praefect: A quorum is not strictly necessary. Two Gitaly nodes and two Praefect nodes are enough for redundancy. -- GitLab From 1335bfbcac3f01f8ac36b382f7046d3011defd61 Mon Sep 17 00:00:00 2001 From: Achilleas Pipinellis Date: Fri, 17 Dec 2021 09:36:33 +0000 Subject: [PATCH 2/2] Apply 1 suggestion(s) to 1 file(s) --- doc/administration/reference_architectures/3k_users.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/administration/reference_architectures/3k_users.md b/doc/administration/reference_architectures/3k_users.md index eb77f1bc8e53d2..c788a73753b414 100644 --- a/doc/administration/reference_architectures/3k_users.md +++ b/doc/administration/reference_architectures/3k_users.md @@ -2145,7 +2145,7 @@ but with smaller performance requirements, several modifications can be consider - Lowering node specs: Depending on your user count, you can lower all suggested node specs as desired. However, it's recommended that you don't go lower than the [general requirements](../../install/requirements.md). - Combining select nodes: Some nodes can be combined to reduce complexity at the cost of some performance: - GitLab Rails and Sidekiq: Sidekiq nodes can be removed and the component instead enabled on the GitLab Rails nodes. - - PostgreSQL and PgBouncer: PgBouncer nodes could be removed and the component instead enabled on PostgreSQL with the Internal Load Balancer pointing to them instead. However please note to enable [Database Load Balancing](../postgresql/database_load_balancing.md) a separate PgBouncer array will still be required. + - PostgreSQL and PgBouncer: PgBouncer nodes could be removed and instead be enabled on PostgreSQL nodes with the Internal Load Balancer pointing to them. However, to enable [Database Load Balancing](../postgresql/database_load_balancing.md), a separate PgBouncer array is still required. - Reducing the node counts: Some node types do not need consensus and can run with fewer nodes (but more than one for redundancy). This will also lead to reduced performance. - GitLab Rails and Sidekiq: Stateless services don't have a minimum node count. Two are enough for redundancy. - Gitaly and Praefect: A quorum is not strictly necessary. Two Gitaly nodes and two Praefect nodes are enough for redundancy. -- GitLab