Auto-commit vs manual commit in Kafka - CLI Comparison

Introduction

Kafka consumers read messages from topics. They must tell Kafka which messages they have processed by committing offsets. Auto-commit does this automatically, while manual commit lets you control when to mark messages as processed.

When you want Kafka to track message processing automatically without extra code.

When you need to ensure messages are fully processed before marking them done.

When processing messages might fail and you want to retry before committing.

When you want to control commit timing to optimize performance.

When you want to avoid losing messages or processing duplicates.

Commands

Starts a Kafka consumer that automatically commits offsets after reading messages. This means Kafka tracks progress without manual intervention.

Terminal

kafka-console-consumer --bootstrap-server localhost:9092 --topic example-topic --group example-group --enable-auto-commit true

Expected Output

This will print messages from example-topic as they arrive, committing offsets automatically.

→

--enable-auto-commit - Enables automatic offset commits.

→

--group - Specifies the consumer group for offset tracking.

Starts a Kafka consumer with auto-commit disabled. You must manually commit offsets in your consumer code to mark messages as processed.

Terminal

kafka-console-consumer --bootstrap-server localhost:9092 --topic example-topic --group example-group --enable-auto-commit false

Expected Output

This will print messages from example-topic but will not commit offsets automatically.

→

--enable-auto-commit - Disables automatic offset commits.

→

--group - Specifies the consumer group for offset tracking.

Shows the current offset positions and lag for the consumer group. Useful to verify if offsets are committed.

Terminal

kafka-consumer-groups --bootstrap-server localhost:9092 --describe --group example-group

Expected Output

TOPIC           PARTITION  CURRENT-OFFSET  LOG-END-OFFSET  LAG  CONSUMER-ID  HOST  CLIENT-ID

example-topic   0          15              20              5    consumer-1   /127.0.0.1  consumer-1

→

--describe - Shows detailed offset and lag information.

→

--group - Specifies the consumer group to inspect.

Key Concept

If you remember nothing else from this pattern, remember: auto-commit is easy but can lose messages on failure, manual commit gives control but needs extra code.

Common Mistakes

Using auto-commit when message processing can fail.

Offsets get committed before processing finishes, causing message loss if failure happens.

Disable auto-commit and commit offsets manually after successful processing.

Forgetting to commit offsets when auto-commit is disabled.

Kafka will keep delivering the same messages repeatedly, causing duplicates.

Add code to commit offsets after processing each message or batch.

Setting auto-commit interval too high.

Offsets commit too late, increasing risk of reprocessing messages after failure.

Set a reasonable auto-commit interval or use manual commit for precise control.

Summary

Auto-commit lets Kafka track message progress automatically but risks losing messages on failure.

Manual commit requires explicit code to mark messages processed, giving full control and safety.

Use kafka-consumer-groups command to check committed offsets and consumer lag.

Practice

1. What is the main difference between auto-commit and manual commit in Kafka consumer offset management?

easy

A. Auto-commit requires manual calls to commit offsets, manual commit commits automatically.

B. Auto-commit disables offset tracking, manual commit enables it.

C. Auto-commit commits offsets automatically at intervals, manual commit requires explicit commit calls.

D. Auto-commit commits offsets only after consumer shutdown, manual commit commits continuously.

Solution

1. Step 1: Understand auto-commit behavior

   Auto-commit commits offsets automatically at regular intervals without user intervention.

2. Step 2: Understand manual commit behavior

   Manual commit requires the consumer to explicitly call commit() after processing messages.

3. Final Answer:

   Auto-commit commits offsets automatically at intervals, manual commit requires explicit commit calls. -> Option C

4. Quick Check:

   Auto-commit = automatic, Manual commit = explicit call [OK]

Hint: Auto-commit is automatic; manual commit needs your call [OK]

Common Mistakes:

• Confusing which method commits automatically
• Thinking manual commit disables offset tracking
• Believing auto-commit commits only on shutdown

2. Which of the following is the correct way to disable auto-commit in Kafka consumer configuration?

easy

A. "enable.auto.commit" : false

B. "auto.commit.enable" : false

C. "auto.commit" : "disable"

D. "enable.auto.commit" : true

Solution

1. Step 1: Identify the correct config key

   The correct Kafka consumer config key to control auto-commit is "enable.auto.commit".

2. Step 2: Identify the correct value to disable auto-commit

   Setting "enable.auto.commit" to false disables auto-commit.

3. Final Answer:

   "enable.auto.commit" : false -> Option A

4. Quick Check:

   Disable auto-commit = enable.auto.commit = false [OK]

Hint: Use "enable.auto.commit" = false to disable auto-commit [OK]

Common Mistakes:

• Using wrong config key names
• Setting true instead of false to disable
• Using string values instead of boolean

3. Given this Kafka consumer code snippet with manual commit:

consumer.poll(Duration.ofMillis(100)).forEach(record -> {
    process(record);
});
consumer.commitSync();

What happens if commitSync() is called before processing the records?

medium

A. Offsets are committed before processing, risking message loss on failure.

B. Offsets are committed after processing, ensuring safe processing.

C. commitSync() throws an exception if called before processing.

D. Offsets are not committed at all.

Solution

1. Step 1: Understand commitSync timing

   commitSync() commits the current offsets to Kafka immediately when called.

2. Step 2: Analyze calling commitSync before processing

   If commitSync() is called before processing, offsets are saved before messages are handled, risking data loss if processing fails.

3. Final Answer:

   Offsets are committed before processing, risking message loss on failure. -> Option A

4. Quick Check:

   Commit before processing = risk of message loss [OK]

Hint: Commit offsets only after processing messages [OK]

Common Mistakes:

• Assuming commitSync waits for processing
• Thinking commitSync throws error if called early
• Believing offsets commit automatically without call

4. You have disabled auto-commit and use manual commit in your Kafka consumer. You notice some offsets are not committed, causing message reprocessing. What is the likely cause?

medium

A. Kafka broker is down, so commits fail silently.

B. Auto-commit is enabled, causing conflicts.

C. You called commit() before processing messages.

D. You forgot to call commit() after processing messages.

Solution

1. Step 1: Check manual commit requirements

   When auto-commit is disabled, the consumer must call commit() explicitly after processing.

2. Step 2: Identify cause of missing commits

   If offsets are not committed, likely commit() was not called after processing, causing reprocessing.

3. Final Answer:

   You forgot to call commit() after processing messages. -> Option D

4. Quick Check:

   Manual commit needs explicit commit() call [OK]

Hint: Always call commit() after processing when auto-commit is off [OK]

Common Mistakes:

• Assuming auto-commit still works when disabled
• Blaming Kafka broker without checking code
• Calling commit() before processing messages

5. You want to ensure exactly-once processing in a Kafka consumer application. Which commit strategy is safer and why?

hard

A. Auto-commit, because it commits offsets automatically without extra code.

B. Manual commit, because you commit offsets only after successful processing.

C. Auto-commit, because it commits offsets after processing each message.

D. Manual commit, because it commits offsets before processing messages.

Solution

1. Step 1: Understand exactly-once processing needs

   Exactly-once means processing each message once and committing offset only after success.

2. Step 2: Compare commit strategies

   Auto-commit commits offsets automatically at intervals, risking committing before processing completes. Manual commit lets you commit only after successful processing.

3. Final Answer:

   Manual commit, because you commit offsets only after successful processing. -> Option B

4. Quick Check:

   Exactly-once needs manual commit after success [OK]

Hint: Commit manually after success for exactly-once processing [OK]

Common Mistakes:

• Assuming auto-commit guarantees exactly-once
• Committing offsets before processing
• Ignoring commit timing importance