Consumer offset commit strategies in Kafka - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a consumer offset in Kafka?

A consumer offset is a marker that shows the position of a consumer in a Kafka topic partition, indicating which messages have been read.

beginner

What are the two main types of offset commit strategies in Kafka?

The two main types are automatic commit and manual commit. Automatic commits happen periodically, while manual commits are controlled by the consumer code.

intermediate

How does automatic offset commit work in Kafka consumers?

Kafka consumers automatically commit offsets at intervals defined by the configuration (e.g., every 5 seconds), which means the consumer periodically saves its position without explicit code.

intermediate

Why might you prefer manual offset commits over automatic commits?

Manual commits give you control to commit offsets only after processing messages successfully, reducing the risk of losing data or processing duplicates if the consumer crashes.

advanced

What is the difference between synchronous and asynchronous manual offset commits?

Synchronous commits block the consumer until the commit is acknowledged, ensuring the offset is saved before continuing. Asynchronous commits send the commit request and continue without waiting, which is faster but less safe.

What does an offset represent in Kafka?

A The timestamp of the last message

B The size of a Kafka topic

C The number of partitions in a topic

D The position of a consumer in a topic partition

An offset marks the position of a consumer in a topic partition, showing which messages have been read.

Which Kafka consumer setting controls automatic offset commits?

A enable.auto.commit

B auto.offset.reset

C fetch.min.bytes

D max.poll.records

The 'enable.auto.commit' setting enables or disables automatic offset commits.

What is a key advantage of manual offset commits?

A Automatic error handling

B Control over when offsets are saved

C Faster message consumption

D No need to write commit code

Manual commits let you decide exactly when to save offsets, improving reliability.

What happens if you use asynchronous offset commits?

A Commit requests are sent without waiting for confirmation

B Consumer blocks until commit is confirmed

C Offsets are never committed

D Consumer automatically retries commits

Asynchronous commits send the commit request and continue without waiting for confirmation.

If a consumer crashes before committing offsets, what risk exists with automatic commits?

A Consumer will not restart

B Messages will be lost forever

C Messages might be processed twice

D Partitions will be deleted

If offsets are committed automatically before processing completes, a crash can cause duplicate processing.

Explain the difference between automatic and manual offset commit strategies in Kafka.

Think about who controls when the offset is saved.

Describe the pros and cons of synchronous versus asynchronous manual offset commits.

Consider speed versus safety.

Practice

1. What is the main purpose of committing consumer offsets in Kafka?

easy

A. To delete old messages from the topic

B. To increase the speed of message production

C. To create new topics automatically

D. To track which messages have been processed to avoid duplicates

Solution

1. Step 1: Understand consumer offset role

   Consumer offsets mark the position of the last processed message in a partition.

2. Step 2: Identify the purpose of committing offsets

   Committing offsets helps Kafka know where to resume reading after a restart, preventing duplicate processing.

3. Final Answer:

   To track which messages have been processed to avoid duplicates -> Option D

4. Quick Check:

   Offset commit = track processed messages [OK]

Hint: Offsets mark progress to avoid reprocessing messages [OK]

Common Mistakes:

• Confusing offset commit with message production speed
• Thinking offsets delete messages
• Believing offsets create topics

2. Which Kafka consumer configuration enables automatic offset commits?

easy

A. enable.auto.commit=false

B. auto.offset.reset=earliest

C. enable.auto.commit=true

D. auto.commit.interval.ms=0

Solution

1. Step 1: Identify the setting for automatic commits

   The setting enable.auto.commit controls if Kafka commits offsets automatically.

2. Step 2: Check the correct value to enable auto commit

   Setting it to true enables automatic offset commits.

3. Final Answer:

   enable.auto.commit=true -> Option C

4. Quick Check:

   enable.auto.commit=true means auto commit enabled [OK]

Hint: Look for enable.auto.commit=true to enable auto commits [OK]

Common Mistakes:

• Confusing auto.offset.reset with auto commit
• Setting enable.auto.commit to false expecting auto commit
• Misunderstanding auto.commit.interval.ms controls commit frequency, not enabling

3. Given this code snippet, what will be the output if the consumer commits offsets manually after processing 3 messages?

consumer.subscribe(["topic"])
for i in range(5):
    msg = consumer.poll(1000)
    print(f"Processing message {i}")
    if i == 2:
        consumer.commitSync()

medium

A. Processing message 0
Processing message 1
Processing message 2
Processing message 3
Processing message 4

B. Processing message 0
Processing message 1
Processing message 2

C. Processing message 0
Processing message 1
Processing message 2
Processing message 3

D. No output due to commit error

Solution

1. Step 1: Analyze the loop and commit timing

   The loop runs 5 times, printing "Processing message i" each time from 0 to 4.

2. Step 2: Understand commitSync effect

   Calling commitSync() at i=2 commits offsets but does not stop processing.

3. Final Answer:

   Processing message 0 Processing message 1 Processing message 2 Processing message 3 Processing message 4 -> Option A

4. Quick Check:

   commitSync commits but loop continues [OK]

Hint: commitSync doesn't stop processing; loop runs fully [OK]

Common Mistakes:

• Assuming commitSync stops the loop
• Thinking only messages before commit are processed
• Confusing commitSync with commitAsync behavior

4. Identify the error in this Kafka consumer code snippet related to offset commits:

consumer.subscribe(["topic"])
while True:
    msg = consumer.poll(1000)
    if msg is not None:
        process(msg)
    consumer.commitAsync()

medium

A. poll() should not have a timeout

B. commitAsync() is called outside the message check, causing commits even when no message is received

C. process(msg) should be called after commitAsync()

D. subscribe() must be called inside the loop

Solution

1. Step 1: Review commitAsync placement

   commitAsync() is called every loop iteration, even if no message is received.

2. Step 2: Understand why this is a problem

   Committing offsets without processing messages can commit the same offset repeatedly or cause unexpected behavior.

3. Final Answer:

   commitAsync() is called outside the message check, causing commits even when no message is received -> Option B

4. Quick Check:

   commitAsync outside message check causes wrong commits [OK]

Hint: Call commit only after processing a message [OK]

Common Mistakes:

• Calling commitAsync regardless of message presence
• Moving subscribe inside the loop unnecessarily
• Misordering process and commit calls

5. You want to ensure your Kafka consumer starts reading from the earliest offset if no committed offset exists, but commits offsets manually only after processing batches of 10 messages. Which configuration and strategy combination is correct?

hard

A. Set auto.offset.reset to earliest and disable enable.auto.commit, then call commitSync() after every 10 messages

B. Set auto.offset.reset to latest and enable enable.auto.commit, commit automatically every 10 messages

C. Set auto.offset.reset to earliest and enable enable.auto.commit, commit manually after every message

D. Set auto.offset.reset to none and disable enable.auto.commit, never commit offsets

Solution

1. Step 1: Choose offset reset policy

   Setting auto.offset.reset to earliest ensures reading from the start if no offset exists.

2. Step 2: Select commit strategy

   Disabling enable.auto.commit allows manual control; calling commitSync() after 10 messages commits offsets in batches.

3. Final Answer:

   Set auto.offset.reset to earliest and disable enable.auto.commit, then call commitSync() after every 10 messages -> Option A

4. Quick Check:

   earliest + manual commit after batch = correct strategy [OK]

Hint: earliest + manual commit after batch = safe and controlled [OK]

Common Mistakes:

• Using latest offset reset when earliest is needed
• Enabling auto commit but expecting manual control
• Not committing offsets causing reprocessing