Backend Server Drain Connections

DE.

Oracle Cloud Infrastructure Load Balancing service provides a way to distribute incoming traffic across multiple backend servers for improved availability and scalability. A backend server can be marked as "draining" to indicate that it should no longer receive new connections. When a backend server is marked to drain connections, the following two actions will occur:

D. All new connections to this backend server are disallowed: The load balancer will stop sending new connections to the backend server that is marked as draining. This means that any new incoming requests will not be sent to this backend server, and the existing connections on this backend server will continue to process the requests until they are completed.

A. All connections to this backend server are forcibly closed after a timeout period: After a configurable timeout period, any remaining connections to the backend server will be forcibly closed. This ensures that all connections are eventually terminated, even if they are long-lived or hanging connections. Once all the connections are closed, the backend server can be safely removed from the backend set.

Option B is incorrect because requests are not redirected to a user-defined error page when a backend server is marked as draining. The load balancer will simply stop sending new connections to this backend server, and existing connections will continue until they are completed.

Option C is incorrect because existing connections will not be immediately closed when a backend server is marked as draining. They will remain open until they are completed or until the configured timeout period has expired.

Option E is also incorrect because connections to the backend server will not remain open until all in-flight requests are completed. New connections will not be allowed, and existing connections will be forcibly closed after a timeout period.