Max fails and fail timeout in Nginx - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does the max_fails directive control in nginx?

It sets the maximum number of failed attempts to connect to a server before nginx considers it unavailable.

beginner

What is the purpose of the fail_timeout directive in nginx?

It defines the time period during which the server is considered unavailable after reaching the max_fails limit.

intermediate

How do max_fails and fail_timeout work together in nginx?

If a server fails max_fails times within fail_timeout, nginx stops sending requests to it for the duration of fail_timeout.

beginner

Example: What happens if max_fails=3 and fail_timeout=30s?

If a server fails 3 times within 30 seconds, nginx marks it as down and stops sending requests to it for 30 seconds.

beginner

Where do you configure max_fails and fail_timeout in nginx?

Inside the upstream block for load balancing servers.

What does max_fails specify in nginx?

A Maximum failed connection attempts before marking server down

B Maximum number of servers in upstream

C Timeout for client requests

D Maximum request size

max_fails sets how many failed attempts to connect to a server are allowed before nginx stops sending requests to it.

What happens during the fail_timeout period after max_fails is reached?

A Server is considered unavailable and skipped

B Server is restarted

C Requests are queued

D Server is removed from config

During fail_timeout, nginx treats the server as down and does not send requests to it.

Where do you set max_fails and fail_timeout in nginx config?

A Inside <code>http</code> block only

B Inside <code>server</code> block

C Inside <code>location</code> block

D Inside <code>upstream</code> block

These directives are set inside the upstream block where backend servers are defined.

If max_fails is 5 and fail_timeout is 10s, what happens if 5 fails occur over 20 seconds?

A Server is marked down immediately

B Server is removed permanently

C Server is not marked down because fails are spread out

D Server is restarted

Fails must happen within the fail_timeout period to mark the server down.

Why use max_fails and fail_timeout in nginx?

A To increase server memory

B To improve load balancing by avoiding bad servers

C To speed up client requests

D To log errors

They help nginx avoid sending requests to servers that are failing, improving reliability.

Explain how nginx uses max_fails and fail_timeout to manage backend servers.

Think about how nginx decides a server is temporarily unavailable.

Describe where and why you would configure max_fails and fail_timeout in an nginx setup.

Consider the role of upstream servers in nginx.

Practice

1. What does the max_fails directive control in an nginx upstream server block?

easy

A. The number of failed attempts before marking the server as down

B. The total number of requests allowed to the server

C. The timeout duration for each request

D. The maximum number of servers in the upstream block

Solution

1. Step 1: Understand the role of max_fails

   The max_fails directive sets how many failed connection attempts to a server are allowed before nginx marks it as down.

2. Step 2: Differentiate from other directives

   It does not limit total requests or set timeouts; it only counts failures.

3. Final Answer:

   The number of failed attempts before marking the server as down -> Option A

4. Quick Check:

   max_fails = failure count limit [OK]

Hint: max_fails counts failures before marking server down [OK]

Common Mistakes:

• Confusing max_fails with request limits
• Thinking max_fails sets timeout duration
• Assuming max_fails controls total servers

2. Which of the following is the correct syntax to set max_fails to 3 and fail_timeout to 30s for a server in nginx?

easy

A. server 192.168.1.1 max_fails 3 fail_timeout 30s;

B. server 192.168.1.1 max_fails=3 fail_timeout=30s;

C. server 192.168.1.1 max_fails:3 fail_timeout:30s;

D. server 192.168.1.1 max_fails(3) fail_timeout(30s);

Solution

1. Step 1: Recall nginx directive syntax

   nginx uses space-separated key value pairs without equal signs inside server blocks.

2. Step 2: Match correct syntax

   server 192.168.1.1 max_fails 3 fail_timeout 30s; uses correct syntax: max_fails 3 fail_timeout 30s; with spaces and semicolon.

3. Final Answer:

   server 192.168.1.1 max_fails 3 fail_timeout 30s; -> Option A

4. Quick Check:

   nginx directives use space-separated key value pairs [OK]

Hint: Use space-separated key value pairs for nginx server parameters [OK]

Common Mistakes:

• Using equal signs (=) in nginx directives
• Using colons (:) instead of spaces
• Adding parentheses around values

3. Given this nginx upstream configuration:

upstream backend {
    server 192.168.0.1 max_fails=2 fail_timeout=10s;
    server 192.168.0.2 max_fails=3 fail_timeout=20s;
}

What happens if 192.168.0.1 fails 3 times within 10 seconds?

medium

A. 192.168.0.2 is marked down instead

B. 192.168.0.1 is marked down for 20 seconds

C. 192.168.0.1 is marked down for 10 seconds

D. 192.168.0.1 is never marked down

Solution

1. Step 1: Understand max_fails and fail_timeout for 192.168.0.1

   max_fails=2 means after 2 failures, server is marked down. fail_timeout=10s means it stays down for 10 seconds.

2. Step 2: Analyze 3 failures within 10 seconds

   3 failures exceed max_fails, so server is marked down for fail_timeout duration (10 seconds).

3. Final Answer:

   192.168.0.1 is marked down for 10 seconds -> Option C

4. Quick Check:

   Failures > max_fails triggers down for fail_timeout [OK]

Hint: Failures over max_fails trigger down for fail_timeout [OK]

Common Mistakes:

• Confusing fail_timeout values between servers
• Assuming server stays down indefinitely
• Marking wrong server down

4. You set max_fails 3 fail_timeout 30s; for a server, but nginx never marks it down even after many failures. What is the likely mistake?

medium

A. Setting fail_timeout to 0

B. Using incorrect syntax like max_fails 3

C. Not enabling proxy_next_upstream directive

D. Using max_fails outside the upstream block

Solution

1. Step 1: Check location of max_fails directive

   max_fails must be inside the upstream block; placing it outside means nginx ignores it.

2. Step 2: Understand effect of incorrect placement

   Incorrect placement means nginx does not apply the max_fails setting, so server is never marked down.

3. Final Answer:

   Using max_fails outside the upstream block -> Option D

4. Quick Check:

   Directive placement affects behavior [OK]

Hint: Ensure max_fails is inside upstream block [OK]

Common Mistakes:

• Using incorrect syntax like max_fails 3
• Assuming fail_timeout 0 disables marking down
• Ignoring proxy_next_upstream role

5. You want to configure nginx so that a backend server is marked down after 5 failures and stays down for 1 minute. Which configuration snippet achieves this correctly?

hard

A. server 10.0.0.1 max_fails=5 fail_timeout=60s;

B. server 10.0.0.1 max_fails 5 fail_timeout 1m;

C. server 10.0.0.1 max_fails=5 fail_timeout=60;

D. server 10.0.0.1 max_fails 5 fail_timeout 60;

Solution

1. Step 1: Confirm correct syntax for max_fails and fail_timeout

   nginx requires space-separated key value pairs without equal signs and time units for fail_timeout, e.g., 60s or 1m for 60 seconds.

2. Step 2: Evaluate options for correctness

   server 10.0.0.1 max_fails 5 fail_timeout 1m; uses correct syntax with spaces and time unit. A uses equals signs which is invalid. C missing time unit 's'. D missing equals and time unit.

3. Final Answer:

   server 10.0.0.1 max_fails 5 fail_timeout 1m; -> Option B

4. Quick Check:

   Use space-separated key value pairs and time units in directives [OK]

Hint: Use space-separated key value pairs, time units like 60s or 1m [OK]

Common Mistakes:

• Omitting time units for fail_timeout
• Using invalid time formats
• Using equals signs in directives