Connection pooling to upstream in Nginx - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Nginx Upstream Connection Pooling Behavior

Given the following nginx upstream configuration, what is the maximum number of idle keepalive connections nginx will maintain to the upstream servers?

Nginx

upstream backend {
    server backend1.example.com max_fails=3 fail_timeout=30s;
    server backend2.example.com max_fails=3 fail_timeout=30s;
    keepalive 10;
}

server {
    location / {
        proxy_pass http://backend;
    }
}

A 10 connections per each upstream server

B 10 connections total shared across all upstream servers

C Unlimited connections, keepalive does not limit connections

D 3 connections total due to max_fails setting

💡 Hint

Think about what the keepalive directive controls in the upstream block.

The keepalive 10; directive sets the maximum number of idle keepalive connections per upstream server (not total across all). So nginx will keep up to 10 connections open per server (20 total with two servers).

❓ Configuration

intermediate

Configuring Upstream Keepalive Connections

Which of the following nginx upstream configurations correctly enables connection pooling with 20 keepalive connections per upstream server?

A

upstream backend {
    server backend1.example.com;
    server backend2.example.com;
    keepalive_connections 20;
}

B

upstream backend {
    server backend1.example.com keepalive=20;
    server backend2.example.com keepalive=20;
}

C

upstream backend {
    server backend1.example.com;
    server backend2.example.com;
    keepalive 20;
}

D

upstream backend {
    server backend1.example.com max_fails=20;
    server backend2.example.com max_fails=20;
}

💡 Hint

Remember the exact syntax for the keepalive directive inside the upstream block.

The keepalive directive is set once inside the upstream block to specify the maximum number of idle keepalive connections per server. It is not set per server and does not use an equals sign.

❓ Troubleshoot

advanced

Diagnosing Connection Pooling Issues

An nginx server is configured with an upstream block using keepalive 15;. However, monitoring shows nginx opens many more than 15 connections to the upstream servers under load. What is the most likely cause?

A The <code>max_fails</code> directive is set too low causing connections to reopen frequently

B The <code>keepalive</code> directive only limits idle connections, active connections can exceed this number

C The <code>keepalive</code> directive must be set inside the server block, not upstream

D Nginx does not support connection pooling with HTTP upstreams

💡 Hint

Consider the difference between idle and active connections in nginx's connection pooling.

The keepalive directive limits the number of idle keepalive connections nginx keeps open to upstream servers. When requests come in, nginx can open additional active connections beyond this limit. So under load, total connections can exceed the keepalive number.

🔀 Workflow

advanced

Implementing Connection Pooling for Upstream Servers

You want to configure nginx to reuse TCP connections to upstream servers to improve performance. Which sequence of steps is correct?

A 2, 1, 3, 4

B 1, 2, 4, 3

C 1, 3, 2, 4

D 1, 2, 3, 4

💡 Hint

Think about the order of defining upstream, enabling keepalive, and configuring proxy headers.

First define the upstream servers, then enable keepalive connections in that block. Next, set proxy_http_version to 1.1 to support keepalive, and finally set the Connection header properly to reuse connections.

✅ Best Practice

expert

Best Practice for Connection Pooling with Multiple Upstream Servers

When configuring connection pooling with multiple upstream servers in nginx, which practice helps ensure efficient connection reuse and load balancing?

A Use a single upstream block with multiple servers and a keepalive directive to share pooled connections across all servers

B Create separate upstream blocks for each server with individual keepalive settings to isolate connections

C Set max_fails to 0 to prevent connection failures from closing pooled connections

D Disable keepalive and rely on nginx to open new connections for each request to balance load evenly

💡 Hint

Consider how nginx manages pooled connections and load balancing across servers.

Using a single upstream block with multiple servers and a keepalive directive allows nginx to maintain pools of idle connections to each server that can be reused efficiently across all servers, improving performance and load distribution.