Error handling in clients in Kafka - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main purpose of error handling in Kafka clients?

To detect, manage, and recover from errors during message production or consumption, ensuring data integrity and system reliability.

beginner

Name two common types of errors Kafka clients must handle.

1. Network errors (e.g., connection loss)
2. Serialization/deserialization errors (e.g., invalid message format)

intermediate

How does a Kafka consumer handle message processing failures to avoid data loss?

By using manual commit of offsets only after successful processing, so failed messages can be retried without losing data.

intermediate

What is a retry mechanism in Kafka clients and why is it important?

A retry mechanism automatically attempts to resend or reprocess messages after transient errors, improving reliability without manual intervention.

advanced

Explain the role of dead-letter queues (DLQ) in Kafka error handling.

DLQs store messages that repeatedly fail processing, allowing developers to inspect and fix problematic data without blocking the main message flow.

Which error should a Kafka client handle to avoid losing messages during consumption?

A Offset commit failure

B UI rendering error

C File system error unrelated to Kafka

D Syntax error in unrelated code

Offset commit failure can cause message loss if not handled properly by retrying or manual commit.

What does a retry mechanism in Kafka clients typically do?

A Deletes failed messages permanently

B Ignores errors silently

C Automatically reprocesses failed messages after a delay

D Sends error logs to the UI

Retry mechanisms help recover from transient errors by reprocessing messages automatically.

Why use a dead-letter queue (DLQ) in Kafka error handling?

A To delete old messages automatically

B To speed up message processing

C To encrypt messages

D To store messages that fail repeatedly for later inspection

DLQs isolate problematic messages so they don't block normal processing.

Which of these is NOT a common Kafka client error type?

A Serialization error

B Database schema error unrelated to Kafka

C Timeout error

D Network error

Database schema errors unrelated to Kafka are outside Kafka client error scope.

How can Kafka consumers avoid processing the same message multiple times after a failure?

A By committing offsets only after successful processing

B By committing offsets before processing

C By ignoring errors

D By deleting messages immediately

Committing offsets after processing ensures failed messages can be retried.

Describe how Kafka clients handle errors during message consumption to ensure no data loss.

Think about when offsets are committed and how retries help.

Explain the purpose and benefits of using a dead-letter queue in Kafka client error handling.

Consider what happens to messages that fail repeatedly.

Practice

1. What is the main purpose of error handling in Kafka clients?

easy

A. To increase the speed of message processing

B. To keep the client stable and responsive during failures

C. To reduce the size of messages sent

D. To automatically create Kafka topics

Solution

1. Step 1: Understand error handling role

   Error handling helps the client manage unexpected problems without crashing.

2. Step 2: Identify the main goal in Kafka clients

   Keeping the client stable and responsive ensures smooth operation even if errors occur.

3. Final Answer:

   To keep the client stable and responsive during failures -> Option B

4. Quick Check:

   Error handling = stability and responsiveness [OK]

Hint: Error handling keeps your client stable and responsive [OK]

Common Mistakes:

• Thinking error handling speeds up processing
• Confusing error handling with message size control
• Assuming error handling creates topics automatically

2. Which syntax correctly wraps a Kafka producer send call to catch exceptions in Java?

easy

A. producer.send(record).catch(e => console.log(e));

B. if (producer.send(record)) { } else { handleError(); }

C. try { producer.send(record); } catch (Exception e) { e.printStackTrace(); }

D. try catch producer.send(record);

Solution

1. Step 1: Identify correct Java try-catch syntax

   Java requires try { ... } catch (Exception e) { ... } to handle exceptions.

2. Step 2: Match syntax with Kafka producer send call

   try { producer.send(record); } catch (Exception e) { e.printStackTrace(); } correctly wraps the send call in try-catch block.

3. Final Answer:

   try { producer.send(record); } catch (Exception e) { e.printStackTrace(); } -> Option C

4. Quick Check:

   Java try-catch syntax = try { producer.send(record); } catch (Exception e) { e.printStackTrace(); } [OK]

Hint: Use try-catch blocks in Java to catch Kafka errors [OK]

Common Mistakes:

• Using if-else instead of try-catch for exceptions
• Using JavaScript syntax in Java code
• Missing braces in try-catch block

3. Given this Java Kafka consumer code snippet, what will be printed if a network error occurs during poll?

try {
  ConsumerRecords records = consumer.poll(Duration.ofMillis(100));
  for (var record : records) {
    System.out.println(record.value());
  }
} catch (WakeupException e) {
  System.out.println("Consumer interrupted");
} catch (Exception e) {
  System.out.println("Error during poll");
}

medium

A. Error during poll

B. Consumer interrupted

C. No output

D. Exception stack trace

Solution

1. Step 1: Identify exception types caught

   WakeupException prints "Consumer interrupted"; all other exceptions print "Error during poll".

2. Step 2: Determine exception for network error

   Network errors throw general exceptions, not WakeupException.

3. Final Answer:

   Error during poll -> Option A

4. Quick Check:

   Network error triggers general Exception = Error during poll [OK]

Hint: General exceptions print "Error during poll" [OK]

Common Mistakes:

• Confusing WakeupException with network errors
• Expecting no output on error
• Assuming stack trace prints automatically

4. Identify the error in this Kafka producer error handling code snippet:

try {
  producer.send(record);
} catch (KafkaException e) {
  System.out.println("Error sending message");
}
producer.close();

medium

A. producer.send() does not throw exceptions

B. Catch block should catch Exception, not KafkaException

C. Missing return statement after catch

D. producer.close() should be inside finally block

Solution

1. Step 1: Check resource cleanup

   producer.close() must run regardless of exceptions to free resources.

2. Step 2: Use finally block for cleanup

   Placing close() inside finally ensures it always executes.

3. Final Answer:

   producer.close() should be inside finally block -> Option D

4. Quick Check:

   Always close resources in finally block [OK]

Hint: Put cleanup code in finally block to always run [OK]

Common Mistakes:

• Closing producer only on success
• Catching too broad or wrong exceptions
• Assuming send() never throws exceptions

5. You want to build a Kafka consumer that retries polling up to 3 times on recoverable errors, then logs and stops. Which approach correctly implements this error handling?

hard

A. Use a loop with try-catch around poll; on exception increment retry count; break after 3 retries; finally close consumer

B. Call consumer.poll() once; if exception, immediately close consumer without retry

C. Wrap poll in try-catch but ignore exceptions and continue polling forever

D. Use multiple nested try-catch blocks without retry logic

Solution

1. Step 1: Understand retry logic requirements

   Retry polling up to 3 times on recoverable errors, then stop and log.

2. Step 2: Identify correct control flow

   Loop with try-catch, count retries, break after 3 attempts, and close consumer in finally block is correct.

3. Final Answer:

   Use a loop with try-catch around poll; on exception increment retry count; break after 3 retries; finally close consumer -> Option A

4. Quick Check:

   Retry with loop and try-catch = Use a loop with try-catch around poll; on exception increment retry count; break after 3 retries; finally close consumer [OK]

Hint: Use loop with try-catch and retry count for controlled retries [OK]

Common Mistakes:

• Not retrying on recoverable errors
• Ignoring exceptions and continuing endlessly
• Closing consumer too early without retries