Offset management in Kafka - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is an offset in Kafka?

An offset is a unique number that identifies the position of a message within a Kafka partition. It helps track which messages have been consumed.

beginner

How does Kafka use offsets to manage message consumption?

Kafka stores offsets to know which messages a consumer has already read. Consumers can resume from the last committed offset to avoid reprocessing messages.

intermediate

What is the difference between automatic and manual offset commits?

Automatic commits save offsets periodically without developer control, while manual commits let developers decide when to save offsets, offering more control and reliability.

intermediate

Why is manual offset management important in Kafka?

Manual offset management helps ensure messages are processed successfully before committing offsets, preventing data loss or duplicate processing.

beginner

What happens if a consumer restarts without committing offsets?

If offsets are not committed, the consumer may re-read messages from the last committed offset or from the beginning, causing duplicate processing.

What does an offset represent in Kafka?

A The position of a message in a partition

B The size of a message

C The timestamp of a message

D The topic name

An offset uniquely identifies the position of a message within a Kafka partition.

Which offset commit method gives you more control over when offsets are saved?

A Automatic commit

B Manual commit

C No commit

D Periodic commit

Manual commit lets developers decide exactly when to save offsets, providing more control.

What risk exists if offsets are committed before processing messages?

A Messages might be lost

B Messages might be processed twice

C Messages might be delayed

D No risk

Committing offsets before processing can cause message loss if the consumer crashes after commit but before processing.

If a consumer restarts without committing offsets, what will happen?

A It will start from the newest message

B It will skip all messages

C It will start from the last committed offset

D It will delete the topic

The consumer resumes from the last committed offset, possibly reprocessing some messages.

Where are offsets typically stored in Kafka?

A In the consumer's local file system

B In the message payload

C In the producer's configuration

D In the Kafka broker's internal __consumer_offsets topic

Kafka stores committed offsets in a special internal topic called __consumer_offsets.

Explain what an offset is and why it is important in Kafka offset management.

Think about how Kafka knows which messages a consumer has read.

Describe the difference between automatic and manual offset commits and when you might use each.

Consider control and reliability when processing messages.

Practice

1. What is the main purpose of offset management in Kafka?

easy

A. To track which messages have been read by a consumer

B. To store the actual message data in Kafka topics

C. To manage the number of partitions in a topic

D. To control the replication factor of Kafka brokers

Solution

1. Step 1: Understand offset management role

   Offset management keeps track of the last message a consumer has read in a partition.

2. Step 2: Differentiate from other Kafka features

   Storing messages, partition count, and replication are unrelated to offset tracking.

3. Final Answer:

   To track which messages have been read by a consumer -> Option A

4. Quick Check:

   Offset management = track read messages [OK]

Hint: Offset management tracks read messages, not data storage [OK]

Common Mistakes:

• Confusing offset with message storage
• Mixing offset with partition or replication management
• Thinking offset controls message content

2. Which of the following is the correct way to manually commit offsets in Kafka consumer API?

easy

A. consumer.offsetCommit()

B. consumer.commitOffset()

C. consumer.saveOffset()

D. consumer.commitSync()

Solution

1. Step 1: Recall Kafka consumer API methods

   The official method to commit offsets manually is commitSync() or commitAsync().

2. Step 2: Identify the exact method name

   Only commitSync() matches the correct Kafka API method for synchronous commit.

3. Final Answer:

   consumer.commitSync() -> Option D

4. Quick Check:

   Manual commit method = commitSync() [OK]

Hint: Manual commit uses commitSync() or commitAsync() [OK]

Common Mistakes:

• Using incorrect method names like commitOffset()
• Confusing commitSync() with offsetCommit()
• Assuming saveOffset() exists

3. Given the following code snippet, what will be the output if the consumer seeks to offset 5 and reads one message?

consumer.assign(Collections.singleton(topicPartition));
consumer.seek(topicPartition, 5);
ConsumerRecords records = consumer.poll(Duration.ofMillis(1000));
for (ConsumerRecord record : records) {
    System.out.println(record.offset());
    break;
}

medium

A. 5

B. 0

C. 1

D. Exception thrown

Solution

1. Step 1: Understand seek behavior

   Calling seek sets the consumer's position to offset 5 in the assigned partition.

2. Step 2: Poll and print offset

   The poll fetches messages starting at offset 5; printing record.offset() outputs 5.

3. Final Answer:

   5 -> Option A

4. Quick Check:

   seek to 5 then poll = offset 5 [OK]

Hint: seek sets start offset; first polled message offset matches [OK]

Common Mistakes:

• Assuming poll starts from offset 0
• Expecting offset 1 instead of 5
• Thinking seek causes an exception

4. What is wrong with the following code snippet for committing offsets manually?

consumer.poll(Duration.ofMillis(1000));
consumer.commitAsync();
consumer.close();

medium

A. consumer.close() should be called before commitAsync()

B. commitAsync() should be called before poll()

C. commitAsync() is called without processing polled records

D. poll() duration is too short for commitAsync()

Solution

1. Step 1: Check offset commit timing

   Offsets should be committed after processing records, not just after poll().

2. Step 2: Identify missing processing step

   The code commits offsets without handling any messages, so it commits offsets that may not be processed.

3. Final Answer:

   commitAsync() is called without processing polled records -> Option C

4. Quick Check:

   Commit after processing, not just after poll [OK]

Hint: Always process records before committing offsets [OK]

Common Mistakes:

• Calling commit before processing messages
• Closing consumer before committing
• Misunderstanding poll duration effect

5. You want to restart a Kafka consumer and continue reading from the last committed offset, but also have the option to start from the beginning if no offset is found. Which approach correctly manages offsets to achieve this?

hard

A. Always call consumer.seekToEnd() before polling messages

B. Use consumer.seekToBeginning() if no committed offset exists, else start from committed offset

C. Manually set offset to 0 every time before polling

D. Disable offset commits and rely on auto.offset.reset = latest

Solution

1. Step 1: Understand offset reset behavior

   If no committed offset exists, consumer can seek to beginning to read all messages.

2. Step 2: Combine offset check and seek

   Check for committed offset; if found, start there; if not, call seekToBeginning() to start fresh.

3. Final Answer:

   Use consumer.seekToBeginning() if no committed offset exists, else start from committed offset -> Option B

4. Quick Check:

   Seek beginning if no offset, else resume from committed [OK]

Hint: Seek beginning only if no committed offset found [OK]

Common Mistakes:

• Always seeking to end loses old messages
• Resetting offset to 0 blindly every time
• Disabling commits causes loss of progress