Details
Description
Dealing with duplicate messages is one of the major issues for teams using Kafka, and Jay Kreps posted a page on implementing an Idempotent Producer to address this issue:
https://cwiki.apache.org/confluence/display/KAFKA/Idempotent+Producer
MapDB 1.0 (https://github.com/jankotek/MapDB) was just released, and either it or Java Chronicle (https://github.com/OpenHFT/Java-Chronicle/) could be embedded within each broker to provide a high-performance, random-access, off-heap store for request IDs.
As Jay points out in his post, global unique request IDs probably aren't needed, but if that need should arise, Twitter's Snowflake service (https://github.com/twitter/snowflake/) might be useful.
Attachments
Issue Links
- is duplicated by
-
KAFKA-4817 Implement idempotent producer
- Resolved