Share
Embed
Transcript
79 slides
-
1 @loicmdivad @PubSapientEng @loicmdivad @PubSapientEng Streaming Apps and Poison Pills:
handle the unexpected with Kafka Streams -
4 @loicmdivad @PubSapientEng 4 @loicmdivad @PubSapientEng Incoming records may be
corrupted, or cannot be handled by the serializer / deserializer. These records are referred to as “poison pills” 1. Log and Crash 2. Skip the Corrupted 3. Sentinel Value Pattern 4. Dead Letter Queue Pattern -
7 @loicmdivad @PubSapientEng 7 @loicmdivad @PubSapientEng Streaming App Poison Pills
1. Log and Crash - Breakfast 2. Skip the Corrupted - Lunch 3. Sentinel Value Pattern - Drink 4. Dead Letter Queue Pattern - Dinner -
10 @loicmdivad @PubSapientEng Really old systems receive raw bytes directly
from message queues 10100110111010101 Exercise #1 - breakfast -
11 @loicmdivad @PubSapientEng Really old systems receive raw bytes directly
from message queues With Kafka (Connect and Streams) we’d like to continuously transform these messages 10100110111010101 Kafka Connect Kafka Brokers Exercise #1 - breakfast -
12 @loicmdivad @PubSapientEng Really old systems receive raw bytes directly
from message queues With Kafka (Connect and Streams) we’d like to continuously transform these messages But we need a deserializer with special decoder to understand each event What happens if we get a buggy implementation of the deserializer? 10100110111010101 Kafka Connect Kafka Brokers Kafka Streams Exercise #1 - breakfast -
13 @loicmdivad @PubSapientEng The Tooling Team They will provide an
appropriate deserializer -
24 @loicmdivad @PubSapientEng ▼ Change consumer group ▼ Manually update
my offsets ▼ Reset my streaming app and set my auto reset to ▽ ▼ Destroy the topic, no message = no poison pill ▽ ▼ My favourite <3 ▽ Don’t Do ▼ Fill an issue and suggest a fix to the tooling team -
26 @loicmdivad @PubSapientEng 26 @loicmdivad @PubSapientEng Log and Crash Like
all consumers, Kafka Streams applications deserialize messages from the broker. The deserialization process can fail. It raises an exception that cannot be caught by our code. Buggy deserializers have to be fixed before the application restarts, by default ... -
36 @loicmdivad @PubSapientEng 36 @loicmdivad @PubSapientEng The Exception Handler in
the call stack Powered by the Flow intelliJ plugin ➞ findtheflow.io -
37 @loicmdivad @PubSapientEng 37 @loicmdivad @PubSapientEng Powered by the Flow
intelliJ plugin ➞ findtheflow.io The Exception Handler in the call stack -
38 @loicmdivad @PubSapientEng 38 @loicmdivad @PubSapientEng Powered by the Flow
intelliJ plugin ➞ findtheflow.io The Exception Handler in the call stack -
39 @loicmdivad @PubSapientEng 39 @loicmdivad @PubSapientEng Powered by the Flow
intelliJ plugin ➞ findtheflow.io The Exception Handler in the call stack -
40 @loicmdivad @PubSapientEng 40 @loicmdivad @PubSapientEng Skip the Corrupted All
exceptions thrown by deserializers are caught by a A handler returns Fail or Continue You can implement your own Handler But the two handlers provided by the library are really basic… let’s explore other methods -
41 @loicmdivad @PubSapientEng 41 @loicmdivad @PubSapientEng All exceptions thrown by
deserializers are caught by a A handler returns Fail or Continue You can implement your own Handler But the two handlers provided by the library are really basic… let’s explore other methods Skip the Corrupted Take Away -
44 @loicmdivad @PubSapientEng • wine • rhum • beer •
champagne • ... -
45 @loicmdivad @PubSapientEng We need to turn the deserialization process
into a pure transformation that cannot crash To do so, we will replace corrupted message by a sentinel value. It’s a special-purpose record (e.g: null, None, Json.Null, etc ...) Sentinel Value Pattern → G H -
46 @loicmdivad @PubSapientEng We need to turn the deserialization process
into a pure transformation that cannot crash To do so, we will replace corrupted message by a sentinel value. It’s a special-purpose record (e.g: null, None, Json.Null, etc ...) This allows downstream processors to recognize and handle such sentinel values Sentinel Value Pattern → G H G H -
47 @loicmdivad @PubSapientEng We need to turn the deserialization process
into a pure transformation that cannot crash To do so, we will replace corrupted message by a sentinel value. It’s a special-purpose record (e.g: null, None, Json.Null, etc ...) This allows downstream processors to recognize and handle such sentinel values With Kafka Streams this can be achieved by implementing a Deserializer Sentinel Value Pattern → G H G H null -
54 @loicmdivad @PubSapientEng 54 @loicmdivad @PubSapientEng Sentinel Value Pattern By
implementing a custom serde we can create a safe . Downstreams now receive a sentinel value indicating a deserialization error. Errors can then be treated correctly, example: monitoring the number of deserialization errors with a custom metric But we lost a lot of information about the error… let’s see a last method -
55 @loicmdivad @PubSapientEng 55 @loicmdivad @PubSapientEng Sentinel Value Pattern By
implementing a custom serde we can create a safe . Downstreams now receive a sentinel value indicating a deserialization error. Errors can then be treated correctly, example: monitoring the number of deserialization errors with a custom metric But we lost a lot of information about the error… let’s see a last method Take Away -
58 @loicmdivad @PubSapientEng Dead Letter Queue Pattern In this method
we will let the deserializer fail. For each failure we will send a message to a topic containing corrupted messages. Each message will have the original content of the input message (for reprocessing) and additional meta data about the failure. With Kafka Streams this can be achieved by implementing a DeserializationExceptionHandler Streaming APP dead letter queue input topic output topic -
63 @loicmdivad @PubSapientEng Fill the headers with some meta data
01061696e0016536f6d6500000005736f6d65206f Value message to hexa -
69 @loicmdivad @PubSapientEng 69 @loicmdivad @PubSapientEng Dead Letter Queue Pattern
You can provide your own implementation of . This lets you use the Producer API to write a corrupted record directly to a quarantine topic. Then you can manually analyse your corrupted records ⚠Warning: This approach have side effects that are invisible to the Kafka Streams runtime. -
70 @loicmdivad @PubSapientEng 70 @loicmdivad @PubSapientEng Dead Letter Queue Pattern
You can provide your own implementation of . This lets you use the Producer API to write a corrupted record directly to a quarantine topic. Then you can manually analyse your corrupted records ⚠Warning: This approach have side effects that are invisible to the Kafka Streams runtime. Take Away -
73 @loicmdivad @PubSapientEng 73 @loicmdivad @PubSapientEng Related Post Kafka Connect
Deep Dive – Error Handling and Dead Letter Queues - by Robin Moffatt Building Reliable Reprocessing and Dead Letter Queues with Apache Kafka - by Ning Xia Handling bad messages using Kafka's Streams API - answer by Matthias J. Sax -
74 @loicmdivad @PubSapientEng 74 @loicmdivad @PubSapientEng Conclusion When using Kafka,
deserialization is the responsibility of the clients. These internal errors are not easy to catch When it’s possible, use Avro + Schema Registry When it’s not possible, Kafka Streams applies techniques to deal with serde errors: - DLQ: By extending a - Sentinel Value: By extending a -
76 @loicmdivad @PubSapientEng 76 @loicmdivad @PubSapientEng Images Photo by rawpixel
on Unsplash Photo by João Marcelo Martins on Unsplash Photo by Jordane Mathieu on Unsplash Photo by Brooke Lark on Unsplash Photo by Jakub Kapusnak on Unsplash Photo by Melissa Walker Horn on Unsplash Photo by Aneta Pawlik on Unsplash -
77 @loicmdivad @PubSapientEng 77 @loicmdivad @PubSapientEng With special thanks to
Robin M. Sylvain L. Giulia B. -
79 @loicmdivad @PubSapientEng Pure HTML Akka Http Server Akka Actor
System Kafka Topic Exercise1 Exercise2 Me, clicking everywhere Akka Stream Kafka