Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update manage-load-balancers.md #1489

Merged
merged 1 commit into from
Dec 19, 2024
Merged

Update manage-load-balancers.md #1489

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 13 additions & 7 deletions documentation/cloud/networking/load-balancers/manage-load-balancers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,6 +113,12 @@ The Load Balancer settings are organized into tabs, each dedicated to a specific

### Flavor

<alert-element type="warning" title="Warning">

During resize or failover operations, all current connections will be terminated, causing temporary disconnects.

</alert-element>

This tab features a summary of the load balancer's configuration and its resources.

<img src="https://assets.gcore.pro/docs/cloud/networking/load-balancers/manage-a-load-balancer/flavor-tab.png" alt="Flavor tab in Load Balancer settings" width="80%">
Expand Down Expand Up @@ -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

<alert-element type="tip" title="Tip">
<alert-element type="Tip" title="Tip">

For optimized performance, we recommend making batch updates of pool settings. To perform comprehensive simultaneous updates, use the <a href="https://api.gcore.com/docs/cloud#tag/Load-Balancers/operation/LoadBalancerPoolInstanceViewSet.patch" target="_blank">Gcore API</a>.

Expand Down Expand Up @@ -269,6 +275,12 @@ When you add the “test” custom tag to your Load Balancer, you essentially la

## Initiate a failover

<alert-element type="warning" title="Warning">

During failover or resize operations, all current connections will be terminated, causing temporary disconnects.

</alert-element>

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.
Expand All @@ -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**.

<alert-element type="warning" title="Warning">

During failover or resize operations, all current connections will be terminated, causing temporary disconnects.

</alert-element>

## Rename a Load Balancer

1\. Navigate to **Cloud** > **Networking**.
Expand Down
Loading