Atomic operations with Lua in Redis

Introduction

Atomic operations make sure a set of commands run all together without interruption. This keeps data safe and correct.

When you want to update multiple keys in Redis at the same time without other commands interfering.

When you need to check a value and change it only if it meets a condition, all in one step.

When you want to do complex logic that Redis commands alone can't handle safely.

When you want to avoid race conditions in a busy system where many clients change data.

When you want to keep your data consistent during multiple related changes.

Syntax

Redis

EVAL script numkeys key [key ...] arg [arg ...]

EVAL runs a Lua script atomically in Redis.

numkeys tells Redis how many keys the script will use.

Examples

Sets the key mykey to myvalue atomically.

Redis

EVAL "return redis.call('set', KEYS[1], ARGV[1])" 1 mykey myvalue

Deletes mykey only if its value matches expectedvalue.

Redis

EVAL "if redis.call('get', KEYS[1]) == ARGV[1] then return redis.call('del', KEYS[1]) else return 0 end" 1 mykey expectedvalue

Sample Program

This script checks if the key counter exists. If not, it sets it to 10. Otherwise, it returns the current value. All happens atomically.

Redis

EVAL "local current = redis.call('get', KEYS[1]) if not current then redis.call('set', KEYS[1], ARGV[1]) return ARGV[1] else return current end" 1 counter 10

Important Notes

Lua scripts in Redis run atomically, so no other commands run in the middle.

Use KEYS array for keys and ARGV array for other arguments inside the Lua script.

Keep scripts short and simple for better performance.

Summary

Atomic operations with Lua keep multiple Redis commands safe and consistent.

Use EVAL to run Lua scripts atomically.

Lua scripts can read and write keys and use arguments for flexible logic.

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