Hello,
In multiple sources I read that Kafka Streams has at-least-once delivery
semantics, meaning that in case of failure, a message can be processed
more than once, but it will not be lost. It is achieved by committing
offset only after the message processing is completely finished and all
offset as id)
-- if the offset in the state is not smaller than the current record's
offset, the current record is a duplicate.
-Matthias
On 2/2/17 6:38 AM, Krzysztof Lesniewski, Nexiot AG wrote:
Hello,
In multiple sources I read that Kafka Streams has at-least-once delivery
semantics, mea
and transactional messaging.
Thanks
Eno
On 2 Feb 2017, at 20:01, Krzysztof Lesniewski, Nexiot AG
wrote:
Thank you Matthias for your answer.
Of course, wherever it is possible I will use idempotent updates, but
unfortunately it does not apply to all my cases.
I though before about the alterna
adds however extra
complexity - we need to maintain the map over time by deleting entries
older than committed offset.
What do you think Matthias?
Kind Regards
Krzysztof Lesniewski
On 03.02.2017 20:02, Matthias J. Sax wrote:
Answers inline.
-Matthias
On 2/3/17 7:37 AM, Krzysztof Lesniewski, N
Ok, so now I understand it. Thank you for all the clarifications :)
Kind Regards
Krzysztof Lesniewski
On 06.02.2017 18:36, Matthias J. Sax wrote:
Completely agree. Very good and deep analysis!
-Matthias
On 2/6/17 3:15 AM, Krzysztof Lesniewski, Nexiot AG wrote:
Thank you Matthias for your
Would be great to get some input on it.
- Krzysztof Lesniewski
On 06.02.2017 08:27, Praveen wrote:
I have a 16 broker kafka cluster. There is a topic with 32 partitions
containing real time data and on the other side, I have 32 boxes w/ 1
consumer reading from these partitions.
Today our deplo
