소비자 예외 처리
Kafka 리스너에서 메시지를 처리하는 동안 발생하는 예외를 원활하게 처리하는 다양한 전략을 알아봅니다.
소비자 예외 처리은(는) CoddyKit의 무료 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 강의입니다. 이것은 4개 중 1번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 강의에는 총 4개의 강의가 포함되어 있습니다.
이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.
Why Handle Kafka Errors?
When your Spring Boot Kafka consumer processes messages, things can go wrong. Maybe a message is malformed, or a dependency fails.
- Data Integrity: Prevent corrupted data from affecting your system.
- Application Stability: Avoid consumer crashes or infinite re-processing loops.
- User Experience: Ensure reliable service by gracefully managing failures.
Proper error handling is key to building robust event-driven applications.
Default Consumer Behavior
By default, if an exception occurs within your @KafkaListener method, Spring Kafka's container will try to re-process the *same* message indefinitely.
This can lead to:
- An infinite loop, consuming CPU cycles.
- Blocking other messages in the partition from being processed.
- Filling up logs with repeated error messages.
We need a strategy to break this cycle and handle errors gracefully.
Basic Try-Catch Block
The simplest way to prevent an infinite re-processing loop for a specific message is to wrap your processing logic in a try-catch block directly within your listener method.
This allows you to catch the exception, log it, and then let the listener method complete normally, causing the offset to be committed.
Try-Catch Example
Here's how a basic try-catch looks within a Spring Boot Kafka listener. This example provides a minimal Spring Boot application structure for compilation.
package com.coddykit;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.kafka.annotation.EnableKafka;
import org.springframework.kafka.annotation.KafkaListener;
import org.springframework.stereotype.Component;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
@SpringBootApplication
@EnableKafka // Enables Kafka listener processing
public class KafkaErrorHandlerApp {
public static void main(String[] args) {
SpringApplication.run(KafkaErrorHandlerApp.class, args);
// In a real app, you'd have a Kafka broker running
// and messages sent to "my-topic" for this listener.
}
@Component
public static class MyKafkaConsumer {
private static final Logger log =
LoggerFactory.getLogger(MyKafkaConsumer.class);
@KafkaListener(topics = "my-topic", groupId = "my-group",
properties = "spring.kafka.consumer.auto-offset-reset=earliest")
public void listen(String message) {
try {
log.info("Received message: {}", message);
// Simulate processing logic that might fail
if (message.contains("error")) {
throw new IllegalArgumentException("Processing error!");
}
log.info("Processed message successfully.");
} catch (Exception e) {
log.error("Error processing message: '{}'. Error: {}",
message, e.getMessage());
// When an error is caught here, the method completes normally,
// and the offset is committed, effectively skipping this message.
}
}
}
}When to Use Try-Catch?
Using try-catch inside the listener is suitable for:
- Expected, recoverable errors: E.g., a specific message format issue you can log and skip.
- Individual message failures: When a single message's failure shouldn't halt the entire consumer.
- Quick fixes: For simple error scenarios where complex framework-level handling isn't needed.
However, for broader, more consistent error handling across multiple listeners, Spring Kafka offers more powerful mechanisms.
Introducing Spring Kafka Error Handlers
Spring Kafka provides a dedicated ErrorHandler interface to handle exceptions that occur during message processing at a higher level, outside your individual listener methods.
This allows for centralized error management and more sophisticated strategies than a simple try-catch.
- Configured at the container factory level.
- Applies to all listeners using that factory.
- Offers various built-in implementations.
Configuring an Error Handler
You configure an ErrorHandler by providing an instance to your ConcurrentKafkaListenerContainerFactory bean. This factory is responsible for creating the listener containers.
Here's how you might set up a factory with a basic error handler:
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.kafka.config.ConcurrentKafkaListenerContainerFactory;
import org.springframework.kafka.core.ConsumerFactory;
import org.springframework.kafka.listener.SeekToCurrentErrorHandler;
@Configuration
public class KafkaConfig {
// Assume consumerFactory is autowired or defined elsewhere.
// In a Spring Boot app, it's typically auto-configured.
private final ConsumerFactory<String, String> consumerFactory;
public KafkaConfig(ConsumerFactory<String, String> consumerFactory) {
this.consumerFactory = consumerFactory;
}
@Bean
public ConcurrentKafkaListenerContainerFactory<String, String>
kafkaListenerContainerFactory() {
ConcurrentKafkaListenerContainerFactory<String, String> factory =
new ConcurrentKafkaListenerContainerFactory<>();
factory.setConsumerFactory(consumerFactory);
// Set a basic error handler
factory.setErrorHandler(new SeekToCurrentErrorHandler());
// This handler prevents the consumer from getting stuck
// on a single message by re-delivering it a few times.
return factory;
}
}SeekToCurrentErrorHandler
The SeekToCurrentErrorHandler is a powerful built-in handler. When an exception occurs, it seeks the partition back to the offset of the failed record.
This means the *same* message will be re-delivered. If it fails again, it re-seeks. By default, it will re-process the message a few times before giving up and advancing the offset for that record.
It's excellent for transient errors, allowing the consumer to move past a problematic message without getting stuck indefinitely.
Custom Error Handling Logic
For highly specific error handling needs, you can implement your own custom ErrorHandler or ConsumerAwareErrorHandler. This gives you full control over what happens when an exception occurs.
- Log to a specific system.
- Send custom alerts (e.g., email, Slack).
- Place messages on a custom 'error queue' (before DLTs).
- Decide whether to commit the offset or re-process.
Remember that complex retry logic and Dead Letter Topics (DLTs) are covered in later lessons!
Quick Check: Error Handling
Consider a Kafka consumer that encounters an exception while processing a message. By default, without any explicit error handling, what is the most likely outcome?
Recap: Handling Consumer Exceptions
In this lesson, we explored fundamental strategies for handling exceptions in Spring Boot Kafka consumers:
- The default behavior of infinite re-processing for unhandled errors.
- Using
try-catchblocks for localized, message-specific error management. - Introducing Spring Kafka's
ErrorHandlerinterface for centralized control. - Configuring a
SeekToCurrentErrorHandlerto prevent consumers from getting stuck. - The flexibility of creating custom error handlers for unique requirements.
These techniques are crucial for building resilient Kafka applications that can gracefully recover from processing failures.
자주 묻는 질문
“소비자 예외 처리” 강의는 무료인가요?
네 — “소비자 예외 처리” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 강의 전체를 잠금 해제할 수 있습니다. Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 강의에는 총 4개의 강의가 포함되어 있습니다.
“소비자 예외 처리”에서 뭘 배우나요?
Kafka 리스너에서 메시지를 처리하는 동안 발생하는 예외를 원활하게 처리하는 다양한 전략을 알아봅니다. 브라우저에서 직접 실행하는 실습 코드로 Advanced Spring Boot 4: Event-Driven Architecture (Kafka)을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.
Advanced Spring Boot 4: Event-Driven Architecture (Kafka)을(를) 시작하는 데 경험이 필요한가요?
사전 경험은 필요하지 않습니다. CoddyKit의 Advanced Spring Boot 4: Event-Driven Architecture (Kafka)은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 1번째 강의입니다.
“소비자 예외 처리” 강의는 얼마나 걸리나요?
대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.
이 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 강의에서 코드를 작성하고 실행할 수 있나요?
네. 모든 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.