AOF (Append Only File) in Redis - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the AOF (Append Only File) in Redis?

AOF is used to save every write operation received by the Redis server. This helps to rebuild the database by replaying these operations after a restart, ensuring data durability.

beginner

How does Redis write data to the AOF file?

Redis appends each write command to the AOF file immediately or periodically, depending on the configured fsync policy, to keep a log of all changes.

intermediate

What are the common fsync policies for AOF in Redis?

The common fsync policies are: always (fsync after every command), everysec (fsync every second), and no (let the OS decide when to write).

intermediate

What is AOF rewriting in Redis and why is it important?

AOF rewriting creates a new, smaller AOF file by rewriting the current dataset as a minimal set of commands. This reduces file size and speeds up recovery.

intermediate

Compare AOF and RDB persistence in Redis.

AOF logs every write operation for better durability but can be slower. RDB snapshots the dataset at intervals, which is faster but risks losing recent changes.

What does AOF stand for in Redis?

A Automatic Output File

B Advanced Operation Format

C Append Only File

D Asynchronous Output Function

AOF stands for Append Only File, which logs every write operation to Redis.

Which fsync policy writes to the AOF file after every command?

A always

B every second

C no

D manual

The 'always' policy fsyncs after every command to ensure maximum durability.

What is the main benefit of AOF rewriting?

A Speeds up recovery by reducing file size

B Disables persistence

C Deletes all data

D Increases file size

AOF rewriting creates a smaller file, making recovery faster.

Which persistence method risks losing recent changes if Redis crashes?

A AOF

B RDB

C Both AOF and RDB

D None

RDB snapshots at intervals, so recent changes after the last snapshot can be lost.

How does Redis use the AOF file during restart?

A It ignores the AOF file

B It deletes the AOF file

C It converts AOF to RDB format

D It replays all commands in the AOF file to rebuild data

Redis replays the commands in the AOF file to restore the database state.

Explain how the AOF persistence works in Redis and why it is useful.

Think about how Redis saves changes to avoid data loss.

Describe the differences between AOF and RDB persistence methods in Redis.

Consider how each method saves data and the trade-offs.

Practice

1.

What is the main purpose of Redis AOF (Append Only File)?

easy

A. To save every write operation for data recovery

B. To compress data for faster network transfer

C. To create backups only once a day

D. To store data in a binary format

Solution

1. Step 1: Understand AOF functionality

   AOF logs every write command to a file to ensure data can be recovered after a crash.

2. Step 2: Compare options with AOF purpose

   Only To save every write operation for data recovery correctly describes saving every write operation for recovery.

3. Final Answer:

   To save every write operation for data recovery -> Option A

4. Quick Check:

   AOF saves writes = B [OK]

Hint: AOF logs all writes to recover data after crashes [OK]

Common Mistakes:

• Thinking AOF compresses data
• Confusing AOF with snapshot backups
• Believing AOF stores data in binary

2.

Which of the following is the correct Redis configuration directive to enable AOF persistence?

?

easy

A. enable_aof on

B. appendonly yes

C. persistence append

D. aof_enable true

Solution

1. Step 1: Recall Redis config syntax for AOF

   The correct directive to enable AOF is appendonly yes.

2. Step 2: Check other options for correctness

   Options A, B, and C are not valid Redis config directives.

3. Final Answer:

   appendonly yes -> Option B

4. Quick Check:

   Enable AOF with appendonly yes [OK]

Hint: Remember: 'appendonly yes' enables AOF in redis.conf [OK]

Common Mistakes:

• Using incorrect directive names
• Confusing AOF with RDB snapshot settings
• Using boolean words like true/on instead of yes

3.

Given the Redis AOF configuration appendfsync everysec, what is the expected behavior?

medium

A. Redis writes AOF data to disk every second

B. Redis never writes AOF data to disk

C. Redis writes every command to disk immediately

D. Redis writes AOF data only on shutdown

Solution

1. Step 1: Understand appendfsync everysec meaning

   This setting tells Redis to sync AOF data to disk once every second.

2. Step 2: Compare with other options

   Redis writes every command to disk immediately means immediate write (appendfsync always), B and D are incorrect behaviors.

3. Final Answer:

   Redis writes AOF data to disk every second -> Option A

4. Quick Check:

   everysec means sync once per second [OK]

Hint: everysec means disk sync once per second, not instantly [OK]

Common Mistakes:

• Confusing everysec with always
• Thinking it never writes to disk
• Assuming writes happen only on shutdown

4.

Identify the error in this Redis AOF configuration snippet:

appendonly yes
appendfsync everyminute

medium

A. appendonly should be no

B. appendfsync must be set to 'never'

C. appendfsync value 'everyminute' is invalid

D. No error, configuration is valid

Solution

1. Step 1: Check valid appendfsync values

   Valid values are 'always', 'everysec', or 'no'. 'everyminute' is not valid.

2. Step 2: Verify appendonly setting

   appendonly yes is correct to enable AOF.

3. Final Answer:

   appendfsync value 'everyminute' is invalid -> Option C

4. Quick Check:

   appendfsync accepts only always, everysec, or no [OK]

Hint: appendfsync only accepts always, everysec, or no [OK]

Common Mistakes:

• Assuming 'everyminute' is valid
• Thinking appendonly yes is wrong
• Believing appendfsync must be 'never'

5.

You want to ensure Redis AOF persistence is safe but also fast. Which configuration balances durability and performance best?

appendonly yes
appendfsync everysec

hard

A. appendonly no and appendfsync no

B. appendonly no and appendfsync always

C. appendonly yes and appendfsync no

D. appendonly yes and appendfsync everysec

Solution

1. Step 1: Understand durability vs performance

   appendonly yes enables AOF persistence; appendfsync everysec syncs data every second, balancing safety and speed.

2. Step 2: Evaluate other options

   Options B and D disable AOF, losing durability; appendonly yes and appendfsync no disables syncing, risking data loss.

3. Final Answer:

   appendonly yes and appendfsync everysec -> Option D

4. Quick Check:

   Enable AOF with everysec sync for balance [OK]

Hint: Use appendonly yes with everysec for good speed and safety [OK]

Common Mistakes:

• Disabling AOF for speed
• Using appendfsync no risking data loss
• Choosing appendfsync always causing slow writes