-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Batch Listener when encountered a poison pill, records after that poison pill are moved to next poll. #3297
Comments
FixedBackOff fixedBackOff = new FixedBackOff(0L, 0L); @service("kafkaStreamListener")
} when there is a poison pill in batch, code after for loop is not executed. |
That's correct.
So, as long as you throw an exception from that |
so in a batch if a record fails (even after retry) records after that failed record are sent to next poll. am i correct. that batch stops at failed record and rest of records are sent to next poll. could you help with this, what happening with my case is, if i have batch of 5 messages and all 5 of them are corrupt messages, so i could see, first message fails and rest 4 are sent to next poll and in next poll, first message fails again and rest are sent to next poll. is this expected behavior. is this right behavior, could you please answer this. @artembilan |
I answer you in other discussion: #2577 (comment). So, yeah, the behavior is expected. |
We are closing this issue. If you see further problems, please feel free to re-open. |
@garyrussell so in a batch if a record fails (even after retry) records after that failed record are sent to next poll. am i correct. that batch stops at failed record and rest of records are sent to next poll. could you help with this, what happening with my case is, if i have batch of 5 messages and all 5 of them are corrupt messages, so i could see, first message fails and rest 4 are sent to next poll and in next poll, first message fails again and rest are sent to next poll. is this expected behavior. thank you
The text was updated successfully, but these errors were encountered: