From d3362c9efa991fdd6f391d522df27e54031bbfde Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Wed, 26 Jun 2024 08:53:27 +0200 Subject: [PATCH] Implemente reorg feedback from DJ --- .../creating_a_dha_cluster.mdx | 18 ++---------------- .../distributed_highavailability.mdx | 13 +++++++++++++ 2 files changed, 15 insertions(+), 16 deletions(-) diff --git a/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/creating_a_dha_cluster.mdx b/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/creating_a_dha_cluster.mdx index d786f46825e..9345a5fe154 100644 --- a/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/creating_a_dha_cluster.mdx +++ b/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/creating_a_dha_cluster.mdx @@ -168,23 +168,9 @@ The following options aren't available when creating your cluster: 1. In the **Connections** section: - When enabled, the **Read-only Workloads** option configures a connection string you can use for read-only operations. This connection enables shadow nodes (non-write leaders) to handle all read-only operations with the goal of lightening the workload on the write leader and improving the cluster's performance. - - If you are configuring this on your own cloud account this option is enabled, you might have to raise the IP address resource limits for the cluster: + When enabled, the **Read-only Workloads** option configures a connection string you can use for read-only operations to lighten the workload on the write leader and improve the cluster's performance. - - For Azure, the IP address quota is Standard Public IP Address. - - - For AWS, the IP address quota is Elastic IP. You might also have to increase the **Network Load Balancers per Region** value. - - !!! Important - - Once you have configured a read-only connection string with your application, read-only workloads are routed to shadow nodes (non-write leaders). The connection is read-only because it accepts read-only queries through the shadow nodes. However, commands that run on read-only connections aren't filtered by BigAnimal, so shadow nodes can still perfom write operations to the contents of database tables. We recommend that you use a Postgres role with minimal read-only privileges for your application or pass `default_transaction_read_only=on` in the connection string. This way, you can avoid write operations on shadow nodes that could cause conflicts between the write leader and the shadow nodes. - See [PGD Proxy read-only routing rules](/pgd/latest/routing/readonly/) for more information. - - !!! Note - Advisory locks aren't replicated between Postgres nodes, so advisory locks taken on a shadow node don't conflict with advisory locks taken on the lead. We recommend that applications that rely on advisory locking avoid using read-only workloads for those transactions. - - See [Read-only workloads](../../overview/02_high_availability/distributed_highavailability/#read-only-workloads) for more information about read-only connections on Distributed High Availability clusters. + See [Read-only workloads](../../overview/02_high_availability/distributed_highavailability/#read-only-workloads) for more information. 1. Select **Next: DB Configuration** diff --git a/product_docs/docs/biganimal/release/overview/02_high_availability/distributed_highavailability.mdx b/product_docs/docs/biganimal/release/overview/02_high_availability/distributed_highavailability.mdx index e5c32678cd1..b3a5a84741e 100644 --- a/product_docs/docs/biganimal/release/overview/02_high_availability/distributed_highavailability.mdx +++ b/product_docs/docs/biganimal/release/overview/02_high_availability/distributed_highavailability.mdx @@ -69,6 +69,19 @@ Since the infrastructure of a Distributed High Availability cluster is almost en Once you have configured a read-only connection string with your application, read-only workloads are routed to shadow nodes (non-write leaders). The connection is read-only because it accepts read-only queries through the shadow nodes. However, commands that run on read-only connections aren't filtered by BigAnimal, so shadow nodes can still perfom write operations to the contents of database tables. We recommend that you use a Postgres role with minimal read-only privileges for your application or pass `default_transaction_read_only=on` in the connection string. This way, you can avoid write operations on shadow nodes that could cause conflicts between the write leader and the shadow nodes. +**IP addresses** + +If you are configuring read-only workload connections on your own cloud account, you might have to raise the IP address resource limits for the cluster: + +- For Azure, the IP address quota is Standard Public IP Address. + +- For AWS, the IP address quota is Elastic IP. You might also have to increase the **Network Load Balancers per Region** value. + +**Advisory locks** + +Advisory locks aren't replicated between Postgres nodes, so advisory locks taken on a shadow node don't conflict with advisory locks taken on the lead. We recommend that applications that rely on advisory locking avoid using read-only workloads for those transactions. + + ## For more information For instructions on creating a distributed high-availability cluster using the BigAnimal portal, see [Creating a distributed high-availability cluster](../../getting_started/creating_a_cluster/creating_a_dha_cluster/).