Lambda Event source mapping MSK consume duplicate offset

Viewed 12

I have 1 question. i am using lambda trigger msk evensource is MSK and set concurrency=1, timeout=14 minutes then i had problem sometimes getting 2 times 1 offset.

For example I has an offset of 20 being processed and it takes 7 minutes to process, then I still get the offset 20 message and process it.

I'm investigating an issue where on the first rebalancing happened the source mapping changed the member ID and got a new consumer and got the message back to position 20 due to the Still Ongoing message out and uncommitted. so it received the message.

I wonder why during lambda's processing when it happens rebalancing

sorry my english is not good

0 Answers
Related