Why Weighted round-robin in Nginx? - Purpose & Use Cases

The Big Idea

What if your website could automatically send more visitors to your fastest servers without you lifting a finger?

The Scenario

Imagine you have several servers to handle web traffic, but some are faster or more powerful than others. You try to send requests one by one to each server in turn, without considering their strength.

The Problem

This simple approach means slower servers get the same load as faster ones, causing delays and unhappy users. Manually adjusting who gets what load is confusing and takes a lot of time.

The Solution

Weighted round-robin lets you assign a weight to each server, so faster servers get more requests automatically. Nginx handles this smoothly, balancing the load fairly without extra effort.

Before vs After

✗ Before

upstream backend {
    server server1.example.com;
    server server2.example.com;
    server server3.example.com;
}

✓ After

upstream backend {
    server server1.example.com weight=3;
    server server2.example.com weight=1;
    server server3.example.com weight=2;
}

What It Enables

This makes your website faster and more reliable by smartly using your servers' strengths.

Real Life Example

A popular online store uses weighted round-robin to send more customers to their powerful servers during sales, avoiding slowdowns and crashes.

Key Takeaways

Manual equal distribution ignores server capacity.

Weighted round-robin balances load based on server strength.

Nginx automates this for better performance and reliability.

Practice

1. What does the weight parameter control in nginx's weighted round-robin load balancing?

easy

A. The maximum number of connections a server can handle

B. The timeout duration for server responses

C. The order in which servers are listed in the config

D. The number of requests sent to a server relative to others

Solution

1. Step 1: Understand the role of weight in load balancing

   The weight defines how many requests a server receives compared to others.

2. Step 2: Relate weight to request distribution

   Higher weight means more requests go to that server, balancing load by capacity.

3. Final Answer:

   The number of requests sent to a server relative to others -> Option D

4. Quick Check:

   Weight controls request share [OK]

Hint: Weight sets request share per server [OK]

Common Mistakes:

• Confusing weight with timeout
• Thinking weight limits connections
• Assuming weight sets server order

2. Which of the following is the correct syntax to assign weights to servers in nginx for weighted round-robin?

easy

A. server backend1.example.com weight:3;

B. server backend1.example.com weight 3;

C. server backend1.example.com weight=3;

D. server backend1.example.com weight(3);

Solution

1. Step 1: Recall nginx upstream server syntax

   Weights are assigned using weight=number with an equal sign and semicolon.

2. Step 2: Check each option's syntax

   Only server backend1.example.com weight=3; uses the correct weight=3; format.

3. Final Answer:

   server backend1.example.com weight=3; -> Option C

4. Quick Check:

   Correct syntax uses equal sign and semicolon [OK]

Hint: Use weight=number; syntax for servers [OK]

Common Mistakes:

• Omitting equal sign
• Using colon instead of equal sign
• Using parentheses incorrectly

3. Given this nginx upstream block:

upstream backend {
  server backend1.example.com weight=3;
  server backend2.example.com weight=1;
}

If 8 requests arrive, how many requests will backend2 receive approximately?

medium

A. 2

B. 6

C. 4

D. 1

Solution

1. Step 1: Calculate total weight

   backend1 weight=3, backend2 weight=1, total = 4.

2. Step 2: Calculate requests for backend2

   Requests for backend2 = (1/4) * 8 = 2.

3. Final Answer:

   2 -> Option A

4. Quick Check:

   Requests proportional to weight [OK]

Hint: Requests split by weight ratio [OK]

Common Mistakes:

• Ignoring total weight sum
• Assigning equal requests despite weights
• Miscounting total requests

4. You configured nginx with weighted round-robin but all servers receive equal requests. What is the most likely cause?

medium

A. nginx does not support weighted round-robin

B. Weights were not specified correctly in the config

C. The servers have identical IP addresses

D. The upstream block is missing the weight directive

Solution

1. Step 1: Understand weighted round-robin requires correct weight syntax

   If weights are missing or incorrect, nginx defaults to equal distribution.

2. Step 2: Analyze the options

   Weights were not specified correctly in the config states weights not specified correctly, which explains equal requests.

3. Final Answer:

   Weights were not specified correctly in the config -> Option B

4. Quick Check:

   Incorrect weights cause equal load [OK]

Hint: Check weight syntax if load is equal [OK]

Common Mistakes:

• Assuming nginx lacks weighted support
• Confusing IP issues with load balancing
• Missing weight directive entirely

5. You have three servers with weights 5, 3, and 2. You want to add a fourth server but keep the total weight sum at 10. What weight should you assign to the new server to maintain the same total weight and keep the relative proportions of the first three servers?

hard

A. 0 (do not add the server)

B. 5

C. 2

D. 1

Solution

1. Step 1: Calculate current total weight

   Sum of existing weights = 5 + 3 + 2 = 10.

2. Step 2: Determine weight for new server

   To keep total sum at 10 when adding a fourth server, assign weight=0 to it.

3. Step 3: Verify proportions

   Weight=0 means no requests to the new server, so first three retain exact proportions (5:3:2 out of total 10).

4. Final Answer:

   0 (do not add the server) -> Option A

5. Quick Check:

   Weight=0 keeps total and proportions unchanged [OK]

Hint: Assign weight=0 to keep total sum and proportions [OK]

Common Mistakes:

• Assigning positive weight that increases total sum
• Forgetting to maintain exact total of 10
• Ignoring impact on relative proportions