From 179e715f42109f63502feba9d8ff6059729cf18f Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Wed, 18 Oct 2023 16:38:57 +0100 Subject: [PATCH] Removed 1000 node limit Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/3.7/bdr/overview.mdx | 3 --- product_docs/docs/pgd/4/limitations.mdx | 2 -- product_docs/docs/pgd/5/limitations.mdx | 3 --- 3 files changed, 8 deletions(-) diff --git a/product_docs/docs/pgd/3.7/bdr/overview.mdx b/product_docs/docs/pgd/3.7/bdr/overview.mdx index c9bc7b72d70..3f38c70c0c1 100644 --- a/product_docs/docs/pgd/3.7/bdr/overview.mdx +++ b/product_docs/docs/pgd/3.7/bdr/overview.mdx @@ -106,9 +106,6 @@ but typical usage would be to have 2-3 standbys per master. Standby nodes don't add additional connections to the mesh network so they are not included in the 32 node recommendation. -BDR currently has hard limit of no more than 1000 active nodes as this is the -current maximum Raft connections allowed. - BDR places a limit that at most 10 databases in any one PostgreSQL instance can be BDR nodes across different BDR node groups. However BDR works best if only one BDR database per PostgreSQL instance is used. diff --git a/product_docs/docs/pgd/4/limitations.mdx b/product_docs/docs/pgd/4/limitations.mdx index a4325a1bfe9..2d4c3891313 100644 --- a/product_docs/docs/pgd/4/limitations.mdx +++ b/product_docs/docs/pgd/4/limitations.mdx @@ -9,8 +9,6 @@ This section covers design limitations of BDR, that should be taken into account - BDR can run hundreds of nodes assuming adequate hardware and network. However, for mesh-based deployments, we generally don’t recommend running more than 48 nodes in one cluster. If extra read scalability is needed beyond the 48 node limit, subscriber only nodes can be added without adding connections to the mesh network. -- BDR currently has a hard limit of no more than 1000 active nodes, as this is the current maximum Raft connections allowed. - - BDR places a limit that at most 10 databases in any one PostgreSQL instance can be BDR nodes across different BDR node groups. However, BDR works best if you use only one BDR database per PostgreSQL instance. - The minimum recommended number of nodes in a group is three to provide fault tolerance for BDR's consensus mechanism. With just two nodes, consensus would fail if one of the nodes was unresponsive. Consensus is required for some BDR operations such as distributed sequence generation. For more information about the consensus mechanism used by EDB Postgres Distributed, see [Architectural details](/pgd/4/architectures/#architecture-details). diff --git a/product_docs/docs/pgd/5/limitations.mdx b/product_docs/docs/pgd/5/limitations.mdx index 866f3c6f1f7..2c16b979914 100644 --- a/product_docs/docs/pgd/5/limitations.mdx +++ b/product_docs/docs/pgd/5/limitations.mdx @@ -13,9 +13,6 @@ into account when planning your deployment. limit, you can add subscriber-only nodes without adding connections to the mesh network. -- PGD currently has a hard limit of no more than 1000 active nodes, as this is - the current maximum Raft connections allowed. - - The minimum recommended number of nodes in a group is three to provide fault tolerance for PGD's consensus mechanism. With just two nodes, consensus would fail if one of the nodes were unresponsive. Consensus is required for some PGD