Resolve Uneven Load Balancing on Oracle Cloud Infrastructure (OCI) Load Balancer

Fixing Uneven Load Distribution on OCI Load Balancer


You have an Oracle Cloud Infrastructure (OCI) load balancer distributing traffic via an evenly-weighted round robin policy to your back-end web servers.

You notice that one of your web servers is receiving more traffic than other web servers.

How can you resolve this to make sure traffic is evenly distributed across all back-end webservers?



Click on the arrows to vote for the correct answer

A. B. C. D.


Sure, I'd be happy to explain the options and help you choose the correct answer.

Option A - Disable cookie-based session persistence on your backend set: Cookie-based session persistence is a mechanism used by the load balancer to maintain session affinity for requests being sent to the backend set. When cookie-based session persistence is enabled, the load balancer ensures that a client's request is always sent to the same backend server that it initially connected to. Disabling cookie-based session persistence can help balance the load across all backend servers, but it can also cause issues if the backend servers require session affinity. In this case, disabling cookie-based session persistence may not be the best solution.

Option B - Change keep-alive setting between the load balancer and backend server: The keep-alive setting controls whether the connection between the load balancer and the backend server remains open after a request is completed. Changing the keep-alive setting may help distribute traffic more evenly, as it will allow the load balancer to switch to another backend server more quickly. However, it's unlikely to be the root cause of the problem, and changing the keep-alive setting may not necessarily resolve the issue.

Option C - Disable SSL configuration associated with your backend set: This option is unlikely to resolve the problem of uneven traffic distribution. Disabling SSL configuration associated with the backend set would make the traffic unencrypted, which could introduce security risks. Additionally, SSL configuration is not directly related to load balancing or traffic distribution.

Option D - Create separate listeners for each backend web server: This option involves creating separate listeners for each backend web server, each with its own port number. By doing this, traffic can be evenly distributed across all backend servers because each server will have a unique listener that can be accessed by the load balancer. This option is the most appropriate solution for the issue of uneven traffic distribution among backend web servers.

Therefore, the correct answer to the question is D - Create separate listeners for each backend web server.