Atomic operations with Lua in Redis - Step-by-Step Execution

Concept Flow - Atomic operations with Lua

Start Lua script

↓

Execute commands inside script

↓

Commands run atomically

↓

Return result

↓

End script execution

Lua scripts in Redis run all commands inside them as one atomic operation, so no other commands run in between.

Execution Sample

Redis

redis.eval("return redis.call('incr', KEYS[1])", 1, 'counter')

This Lua script increments the 'counter' key atomically and returns the new value.

Execution Table

Step	Action	Command Executed	Key State Before	Key State After	Result
1	Start script	-	-	-	-
2	Call redis.call('incr', 'counter')	INCR counter	counter=5	counter=6	6
3	Return result	-	-	-	6
4	End script	-	-	-	-

💡 Script ends after returning the incremented value; all commands ran atomically.

Variable Tracker

Variable	Start	After Step 2	Final
counter	5	6	6

Key Moments - 2 Insights

Why does the counter not change between steps 2 and 3?

Because the Lua script runs atomically, no other commands can run between steps 2 and 3, so the counter stays at 6 as updated in step 2.

Can other Redis commands run while the Lua script is executing?

No, Redis blocks other commands during the Lua script execution to ensure atomicity, as shown by the uninterrupted steps in the execution_table.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'counter' after step 2?

A 6

B 5

C 7

D Undefined

💡 Hint

Check the 'Key State After' column in step 2 of the execution_table.

At which step does the Lua script return the incremented value?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the 'Result' column in the execution_table for the return action.

If another client tries to increment 'counter' during the script execution, what happens?

A It increments immediately

B It causes an error

C It waits until the script finishes

D It increments before the script

💡 Hint

Refer to the key_moments section about atomicity and command blocking.

Concept Snapshot

Lua scripts in Redis run atomically.
All commands inside a script execute without interruption.
Use redis.call() to run Redis commands inside Lua.
No other commands run until the script finishes.
This ensures consistent and safe updates.

Full Transcript

This visual execution trace shows how Redis runs Lua scripts atomically. The script starts and executes the INCR command on the 'counter' key. The counter value changes from 5 to 6 inside the script. Because the script runs atomically, no other commands can run between these steps. The script then returns the new counter value 6 and ends. This atomic behavior prevents race conditions and ensures data consistency in Redis.

Practice

1. What is the main benefit of using Lua scripts with Redis EVAL command?

easy

A. It ensures multiple commands run atomically without interference.

B. It speeds up Redis server startup time.

C. It allows Redis to store Lua scripts permanently.

D. It automatically backs up Redis data to disk.

Solution

1. Step 1: Understand atomicity in Redis

   Atomicity means commands run fully or not at all, preventing partial updates.

2. Step 2: Role of Lua scripts with EVAL

   Lua scripts run all commands inside them as a single atomic operation in Redis.

3. Final Answer:

   It ensures multiple commands run atomically without interference. -> Option A

4. Quick Check:

   Atomic operations = safe multi-command execution [OK]

Hint: Lua scripts run all commands atomically in Redis [OK]

Common Mistakes:

• Thinking Lua scripts speed up server startup
• Confusing script storage with atomicity
• Assuming Lua scripts backup data automatically

2. Which of the following is the correct syntax to run a Lua script that increments a Redis key counter by 1 using EVAL?

easy

A. EVAL "return redis.call('INCR', 'counter')" 0

B. EVAL "return redis.call('INCR', ARGV[1])" 1 counter

C. EVAL "return redis.call('INCR', KEYS[1])" 0 counter

D. EVAL "return redis.call('INCR', KEYS[1])" 1 counter

Solution

1. Step 1: Understand EVAL syntax

   EVAL script numkeys key1 key2 ... args ...; KEYS[] holds keys, ARGV[] holds arguments.

2. Step 2: Identify correct usage for increment

   Since 'counter' is a key, it should be passed as KEYS[1] with numkeys=1.

3. Final Answer:

   EVAL "return redis.call('INCR', KEYS[1])" 1 counter -> Option D

4. Quick Check:

   Use KEYS for keys, ARGV for arguments [OK]

Hint: Keys go in KEYS[], count keys correctly [OK]

Common Mistakes:

• Passing keys in ARGV instead of KEYS
• Setting numkeys to 0 when keys are used
• Using string literal instead of KEYS[1]

3. Given the Lua script run with EVAL below, what will be the output if the key visits does not exist initially?

EVAL "local v = redis.call('GET', KEYS[1]) if not v then v = 0 end v = v + 1 redis.call('SET', KEYS[1], v) return v" 1 visits

medium

A. nil

B. 1

C. 0

D. Error: attempt to perform arithmetic on a nil value

Solution

1. Step 1: Analyze GET result when key missing

   redis.call('GET', KEYS[1]) returns nil if key doesn't exist.

2. Step 2: Check the if condition

   if not v then v = 0 end executes since v is nil, setting v to 0.

3. Step 3: Perform arithmetic and SET

   v = 0 + 1 = 1; redis.call('SET', KEYS[1], 1); return 1.

4. Final Answer:

   1 -> Option B

5. Quick Check:

   Nil handled by if not v, outputs 1 [OK]

Hint: Script checks nil before math, outputs 1 [OK]

Common Mistakes:

• Overlooking the 'if not v then v = 0 end' check
• Assuming nil causes arithmetic error despite handling
• Thinking GET nil leads to error without reading full script

4. Identify the error in this Lua script used with Redis EVAL:

EVAL "local count = redis.call('GET', KEYS[1]) count = tonumber(count) + 1 redis.call('SET', KEYS[1], count) return count" 1 visits

medium

A. Missing check if count is nil before tonumber conversion.

B. Incorrect number of keys specified in EVAL command.

C. Using redis.call instead of redis.pcall causes failure.

D. The return statement should be outside the script string.

Solution

1. Step 1: Understand tonumber behavior

   tonumber(nil) returns nil, so nil + 1 causes error.

2. Step 2: Check script for nil handling

   Script does not check if count is nil before adding 1, causing runtime error if key missing.

3. Final Answer:

   Missing check if count is nil before tonumber conversion. -> Option A

4. Quick Check:

   Always check nil before tonumber and math [OK]

Hint: Check nil before tonumber and math operations [OK]

Common Mistakes:

• Assuming tonumber(nil) returns 0
• Ignoring nil checks before arithmetic
• Confusing redis.call and redis.pcall usage

5. You want to atomically increment a Redis key page_views only if its current value is less than 100. Which Lua script snippet correctly implements this logic using EVAL?

hard

A. local v = redis.call('GET', KEYS[1]) if v < 100 then redis.call('INCR', KEYS[1]) return v + 1 else return v end

B. local v = tonumber(redis.call('GET', KEYS[1])) if v <= 100 then redis.call('INCR', KEYS[1]) return v + 1 else return v end

C. local v = tonumber(redis.call('GET', KEYS[1]) or '0') if v < 100 then redis.call('INCR', KEYS[1]) return v + 1 else return v end

D. local v = tonumber(redis.call('GET', KEYS[1]) or '0') if v <= 100 then redis.call('INCR', KEYS[1]) return v + 1 else return v end

Solution

1. Step 1: Handle missing key safely

   Using 'or "0"' ensures tonumber gets '0' if key missing, avoiding nil errors.

2. Step 2: Check condition and increment

   Condition 'v < 100' matches requirement to increment only if less than 100.

3. Step 3: Return updated or current value

   Returns v+1 if incremented, else returns current v.

4. Final Answer:

   local v = tonumber(redis.call('GET', KEYS[1]) or '0') if v < 100 then redis.call('INCR', KEYS[1]) return v + 1 else return v end -> Option C

5. Quick Check:

   Safe nil handling + correct condition = local v = tonumber(redis.call('GET', KEYS[1]) or '0') if v < 100 then redis.call('INCR', KEYS[1]) return v + 1 else return v end [OK]

Hint: Use 'or "0"' to avoid nil, check '< 100' strictly [OK]

Common Mistakes:

• Not handling nil key values
• Using <= 100 instead of < 100
• Forgetting to convert GET result to number