Persistence and performance trade-off in Redis - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable Redis snapshotting with a save interval of 60 seconds and 1000 changes.

Redis

save [1] 1000

Drag options to blanks, or click blank then click option'

A30

B120

C60

D300

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a very short interval which may impact performance.

Confusing the time interval with the number of changes.

The save directive sets Redis to snapshot the dataset every specified seconds if at least the given number of changes occurred. Here, 60 seconds is the correct interval.

2fill in blank

medium

Complete the code to disable AOF persistence in Redis configuration.

Redis

appendonly [1]

Drag options to blanks, or click blank then click option'

Ano

Boff

Cauto

Dyes

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'off' instead of 'no' which is not valid in Redis config.

Confusing appendonly with save directives.

Setting appendonly no disables the Append Only File persistence in Redis, improving performance but risking data loss on crashes.

3fill in blank

hard

Fix the error in the Redis configuration line to set the AOF fsync policy to every second.

Redis

appendfsync [1]

Drag options to blanks, or click blank then click option'

Ano

Beverysec

Calways

Dsometimes

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'always' which syncs after every write and hurts performance.

Using 'no' which disables fsync and risks data loss.

The correct value for fsync every second is everysec. Other options either cause too frequent syncing or disable it.

4fill in blank

hard

Fill both blanks to configure Redis to save snapshots every 900 seconds if at least 1 change occurred and disable AOF.

Redis

save [1] 1
appendonly [2]

Drag options to blanks, or click blank then click option'

A900

Byes

Cno

D60

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up the save interval with the number of changes.

Using 'yes' instead of 'no' to disable appendonly.

Setting save 900 1 means Redis saves a snapshot every 900 seconds if at least one change happened. Setting appendonly no disables AOF persistence.

5fill in blank

hard

Fill all three blanks to configure Redis to save snapshots every 300 seconds if 10 changes occurred, enable AOF, and set fsync policy to always.

Redis

save [1] 10
appendonly [2]
appendfsync [3]

Drag options to blanks, or click blank then click option'

A60

Byes

Calways

D300

Attempts:

3 left

💡 Hint

Common Mistakes

Using 60 instead of 300 for save interval.

Setting appendonly to 'no' which disables persistence.

Choosing 'everysec' instead of 'always' for fsync.

This configuration saves snapshots every 300 seconds if 10 changes happened, enables AOF persistence, and sets fsync to always for maximum durability but lower performance.

Practice

1. Which Redis persistence method saves data at specific time intervals, balancing durability and performance?

easy

A. No persistence

B. AOF logging

C. RDB snapshots

D. In-memory only

Solution

1. Step 1: Understand Redis persistence options

   Redis offers RDB snapshots and AOF logging for persistence.

2. Step 2: Identify method saving data at intervals

   RDB snapshots save data periodically, while AOF logs every write.

3. Final Answer:

   RDB snapshots -> Option C

4. Quick Check:

   Persistence by snapshots = RDB snapshots [OK]

Hint: Snapshots save periodically, logs save every write [OK]

Common Mistakes:

• Confusing AOF with snapshots
• Thinking no persistence saves data
• Assuming in-memory is persistent

2. Which Redis configuration option enables Append Only File (AOF) persistence?

easy

A. appendonly yes

B. appendonly no

C. save 900 1

D. stop-writes-on-bgsave-error no

Solution

1. Step 1: Identify AOF enabling option

   The option to enable AOF is 'appendonly yes'.

2. Step 2: Differentiate from snapshot options

   'save 900 1' relates to RDB snapshots, not AOF.

3. Final Answer:

   appendonly yes -> Option A

4. Quick Check:

   Enable AOF = appendonly yes [OK]

Hint: Enable AOF with 'appendonly yes' in config [OK]

Common Mistakes:

• Using 'appendonly no' disables AOF
• Confusing 'save' with AOF setting
• Misreading unrelated config options

3. Given Redis configured with RDB snapshots every 60 seconds and AOF enabled with 'appendfsync everysec', what is the maximum data loss if Redis crashes?

medium

A. Up to 1 second of data loss

B. Up to 60 seconds of data loss

C. No data loss

D. Up to 5 minutes of data loss

Solution

1. Step 1: Understand RDB snapshot interval

   Snapshots save every 60 seconds, so up to 60 seconds loss if using RDB only.

2. Step 2: Consider AOF 'appendfsync everysec'

   This setting syncs AOF every second, limiting loss to up to 1 second.

3. Step 3: Combine effects

   With both RDB and AOF enabled, Redis prioritizes AOF for recovery of recent writes, so maximum data loss is 1 second.

4. Final Answer:

   Up to 1 second of data loss -> Option A

5. Quick Check:

   AOF everysec = up to 1s loss [OK]

Hint: Max loss = AOF fsync interval when AOF enabled [OK]

Common Mistakes:

• Thinking RDB interval dominates with AOF enabled
• Ignoring AOF sync policy
• Confusing 'everysec' with immediate sync

4. You configured Redis with 'appendonly yes' but notice no AOF file is created. What is the most likely cause?

medium

A. AOF file is corrupted

B. RDB snapshots disabled

C. Disk is full

D. Redis was not restarted after config change

Solution

1. Step 1: Check if config changes take effect immediately

   Changing 'appendonly yes' requires Redis restart to activate.

2. Step 2: Rule out other causes

   Disk full or corruption would cause errors, snapshots don't affect AOF creation.

3. Final Answer:

   Redis was not restarted after config change -> Option D

4. Quick Check:

   Config changes need restart [OK]

Hint: Restart Redis after enabling AOF [OK]

Common Mistakes:

• Assuming snapshots affect AOF file
• Ignoring need to restart Redis
• Blaming disk issues without checking

5. You want Redis to minimize data loss but can tolerate some performance cost. Which configuration best fits this need?

hard

A. Enable RDB snapshots every 15 minutes and disable AOF

B. Enable AOF with 'appendfsync everysec' and RDB snapshots every 5 minutes

C. Enable AOF with 'appendfsync always' and disable RDB snapshots

D. Disable both AOF and RDB snapshots for max speed

Solution

1. Step 1: Understand data loss vs performance trade-off

   'appendfsync always' is safest but slowest; 'everysec' balances safety and speed.

2. Step 2: Combine AOF and snapshots for better durability

   Using both reduces data loss and improves recovery options.

3. Step 3: Evaluate options

   Enable AOF with 'appendfsync everysec' and RDB snapshots every 5 minutes balances minimal data loss with acceptable performance cost.

4. Final Answer:

   Enable AOF with 'appendfsync everysec' and RDB snapshots every 5 minutes -> Option B

5. Quick Check:

   Balanced persistence = AOF everysec + snapshots [OK]

Hint: Use AOF everysec plus snapshots for balance [OK]

Common Mistakes:

• Choosing 'appendfsync always' for performance
• Disabling persistence for safety
• Relying on snapshots alone for minimal loss