Why persistence matters in Redis - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is persistence important in Redis?

Redis is an in-memory database. What is the main reason to enable persistence in Redis?

A To save data to disk so it is not lost if the server restarts or crashes

B To speed up data retrieval by caching data in memory

C To allow multiple clients to connect simultaneously

D To encrypt data for security purposes

💡 Hint

Think about what happens if the server loses power suddenly.

Persistence saves data to disk so Redis can recover data after a restart or crash. Without persistence, all data in memory would be lost.

❓ query_result

intermediate

What happens to data without persistence?

Assume Redis is running without any persistence enabled. You add a key-value pair user:1 -> 'Alice'. Then the server crashes and restarts. What will be the result of GET user:1 after restart?

A It returns an empty string because the key exists but has no value

B It returns null because data was lost after restart

C It returns an error because the key is corrupted

D It returns 'Alice' because data is stored in memory

💡 Hint

Consider what happens to in-memory data when the server restarts without saving it.

Without persistence, Redis only keeps data in memory. On restart, memory is cleared, so keys are lost and GET returns null.

📝 Syntax

advanced

Which Redis command enables snapshot persistence?

Which command configures Redis to save snapshots of the dataset to disk at regular intervals?

A SAVE

B PERSIST

C BGSAVE

D CONFIG SET save

💡 Hint

Think about how to configure automatic snapshot intervals.

CONFIG SET save sets the snapshotting intervals in Redis configuration. SAVE and BGSAVE trigger immediate snapshots. PERSIST removes expiration from keys.

❓ optimization

advanced

Choosing persistence for performance and durability

You want Redis to persist data but minimize performance impact. Which persistence method balances durability and speed best?

A RDB snapshots only

B No persistence, rely on replication

C AOF with fsync every second

D AOF (Append Only File) with fsync always

💡 Hint

Consider how often data is written to disk and its effect on speed.

AOF with fsync every second writes data asynchronously, providing good durability with less performance cost than fsync always. RDB snapshots are faster but less durable. No persistence risks data loss.

🔧 Debug

expert

Why does Redis lose data despite persistence enabled?

You enabled both RDB snapshots and AOF persistence in Redis. However, after a server crash, some recent writes are missing. What is the most likely cause?

A AOF fsync policy is set to 'no' causing delayed writes to disk

B RDB snapshots overwrite AOF file causing data loss

C Redis does not support combining RDB and AOF persistence

D The server crashed before Redis could start

💡 Hint

Check how often Redis flushes AOF data to disk.

If AOF fsync is set to 'no', Redis buffers writes in memory and writes to disk less frequently, risking data loss on crash. RDB and AOF can be combined safely. Server crash timing matters.

Practice

1. Why is persistence important in Redis?

easy

A. It encrypts data for security during transmission.

B. It speeds up data retrieval by caching in memory.

C. It saves data to disk to prevent data loss after a restart.

D. It automatically deletes old data to free memory.

Solution

1. Step 1: Understand persistence purpose

   Persistence means saving data to disk so it is not lost when Redis restarts or crashes.

2. Step 2: Compare options

   Only the option stating 'It saves data to disk to prevent data loss after a restart.' describes saving data to disk to prevent loss. Others describe caching, deleting, or encryption, which are unrelated to persistence.

3. Final Answer:

   It saves data to disk to prevent data loss after a restart. -> Option C

4. Quick Check:

   Persistence = saving data safely [OK]

Hint: Persistence means saving data to disk to avoid loss [OK]

Common Mistakes:

• Confusing persistence with caching
• Thinking persistence deletes data
• Mixing persistence with encryption

2. Which Redis configuration option controls how often data is saved to disk?

easy

A. save

B. maxmemory-policy

C. appendonly

D. timeout

Solution

1. Step 1: Identify persistence settings

   Redis uses the save option to specify intervals for saving snapshots to disk.

2. Step 2: Eliminate other options

   maxmemory-policy controls eviction, appendonly enables AOF persistence, and timeout sets client timeout, not snapshot frequency.

3. Final Answer:

   save -> Option A

4. Quick Check:

   save = snapshot frequency setting [OK]

Hint: Remember 'save' sets snapshot intervals in Redis config [OK]

Common Mistakes:

• Confusing appendonly with save
• Thinking maxmemory-policy controls saving
• Mixing timeout with persistence

3. Given this Redis config snippet:

save 900 1
save 300 10
save 60 10000

What does this configuration mean?

medium

A. Save data every 900 seconds if at least 1 key changed, every 300 seconds if 10 keys changed, and every 60 seconds if 10000 keys changed.

B. Save data every 900 seconds regardless of changes, every 300 seconds if 10 keys changed, and every 60 seconds if 10000 keys changed.

C. Save data only once after 900 seconds, ignoring key changes.

D. Save data every 900 seconds if 900 keys changed, every 300 seconds if 300 keys changed, and every 60 seconds if 60 keys changed.

Solution

1. Step 1: Understand Redis save syntax

   Each line means: save after X seconds if at least Y keys changed. For example, save 900 1 means save after 900 seconds if 1 or more keys changed.

2. Step 2: Match lines to meaning

   Lines specify different intervals and minimum changed keys: 900s/1 key, 300s/10 keys, 60s/10000 keys.

3. Final Answer:

   Save data every 900 seconds if at least 1 key changed, every 300 seconds if 10 keys changed, and every 60 seconds if 10000 keys changed. -> Option A

4. Quick Check:

   save X Y means save after X seconds if Y keys changed [OK]

Hint: Remember save X Y means save after X seconds if Y keys changed [OK]

Common Mistakes:

• Ignoring the minimum changed keys condition
• Assuming save happens regardless of changes
• Mixing seconds and keys numbers

4. You set appendonly yes in Redis config but data is not saved after restart. What is the likely problem?

medium

A. The appendfsync setting is set to 'no', so AOF is disabled.

B. The Redis server was not restarted after changing the config.

C. The save option must be enabled for AOF to work.

D. The appendonly.aof file is missing or corrupted.

Solution

1. Step 1: Understand AOF persistence

   Setting appendonly yes enables AOF persistence, which logs every write operation to a file.

2. Step 2: Identify why data might not persist

   If the AOF file is missing or corrupted, Redis cannot restore data on restart, causing data loss despite the setting.

3. Final Answer:

   The appendonly.aof file is missing or corrupted. -> Option D

4. Quick Check:

   AOF file missing = no data restored [OK]

Hint: Check if AOF file exists and is valid when appendonly is yes [OK]

Common Mistakes:

• Thinking appendfsync 'no' disables AOF (it controls fsync frequency)
• Assuming save option affects AOF
• Forgetting to restart Redis after config changes

5. You want to ensure Redis never loses more than 5 minutes of data after a crash. Which persistence setup is best?

hard

A. Enable RDB snapshots every 900 seconds and disable AOF.

B. Enable both RDB snapshots every 300 seconds and AOF with appendfsync 'everysec'.

C. Enable AOF with appendfsync set to 'everysec' and disable RDB snapshots.

D. Disable both RDB and AOF to improve performance.

Solution

1. Step 1: Understand persistence options

   RDB snapshots save data at intervals (e.g., every 300 seconds). AOF logs every write and can fsync every second.

2. Step 2: Match requirement to config

   To lose no more than 5 minutes (300 seconds) of data, snapshots alone are risky. Combining snapshots every 300s with AOF fsync every second minimizes data loss.

3. Step 3: Evaluate options

   The option to enable both RDB snapshots every 300 seconds and AOF with appendfsync 'everysec' enables both methods with appropriate intervals, ensuring minimal data loss. Others either save less often or disable persistence.

4. Final Answer:

   Enable both RDB snapshots every 300 seconds and AOF with appendfsync 'everysec'. -> Option B

5. Quick Check:

   Combine snapshots + AOF for best data safety [OK]

Hint: Use both snapshots and AOF for minimal data loss [OK]

Common Mistakes:

• Relying on snapshots alone for short data loss windows
• Disabling persistence to improve speed
• Setting appendfsync to 'no' or 'always' incorrectly