Questions and answers
To get balancer logs, contact technical support.
By default, balancer logs are not collected, but upon a prior request, logging can be enabled for a limited time to analyze issues.
VK Cloud supports three balancing methods:
LEAST_CONNECTIONS— the backend with the fewest established connections is used.ROUND_ROBIN— all backends are iterated through sequentially.SOURCE_IP— a backend is selected randomly and assigned to the session for a specific client IP address.
The balancing method is selected when adding a balancing rule in the management console.
Yes, a similar balancing method is SOURCE_IP. In this method, the server handling the request is selected arbitrarily and pinned to a session for a specific client IP address.
Timeouts for a balancer are set when adding a balancing rule in the management console or using OpenStack CLI. A balancing rule can also be added when creating a balancer.
- Client data — client inactivity timeout.
- Member connect — timeout for establishing a connection between the balancer and the server.
- Member data — server inactivity timeout.
- TCP inspect — timeout for waiting for additional TCP packets to inspect the content.
For highly loaded systems of 10 Gbit/s and above, a dedicated balancer with an individual configuration template (flavor) is required. For more details, see the article Creating a load balancer with an individual configuration template.