diff --git a/documentation/cloud/networking/load-balancers/manage-load-balancers.md b/documentation/cloud/networking/load-balancers/manage-load-balancers.md index 1eb13b23..8488c2df 100644 --- a/documentation/cloud/networking/load-balancers/manage-load-balancers.md +++ b/documentation/cloud/networking/load-balancers/manage-load-balancers.md @@ -113,6 +113,12 @@ The Load Balancer settings are organized into tabs, each dedicated to a specific ### Flavor + + +During resize or failover operations, all current connections will be terminated, causing temporary disconnects. + + + This tab features a summary of the load balancer's configuration and its resources. Flavor tab in Load Balancer settings @@ -175,7 +181,7 @@ It's also not possible to use both TCP 80 and HTTP 80. The reason is that HTTP i #### Pool settings - + For optimized performance, we recommend making batch updates of pool settings. To perform comprehensive simultaneous updates, use the Gcore API. @@ -269,6 +275,12 @@ When you add the “test” custom tag to your Load Balancer, you essentially la ## Initiate a failover + + +During failover or resize operations, all current connections will be terminated, causing temporary disconnects. + + + The failover mechanism automatically detects Load Balancers that have failed or demonstrate degraded performance. When you initiate a failover, the traffic is redirected to an alternate Load Balancer within your network infrastructure. The second balancer immediately takes over the duties of the failed one without interrupting the availability of your application. @@ -295,12 +307,6 @@ To initiate a failover: The failover might take a few minutes to complete. During this time, the Load Balancer provisioning status will change to **Updating**. - - -During failover or resize operations, all current connections will be terminated, causing temporary disconnects. - - - ## Rename a Load Balancer 1\. Navigate to **Cloud** > **Networking**.