-
-
Notifications
You must be signed in to change notification settings - Fork 507
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
Barrier causes uncontrolled execution flow #1300
Comments
kafkajs/src/consumer/runner.js Lines 369 to 386 in 1876abc
|
Adding This will trigger concurrently I am not sure about impact on |
Can you see if this is reproducible with #1258? The barrier is going to be gone as soon as we merge that, in which case we don't need to spend time and effort on debugging this in the current version. |
will check now |
@Nevon The issue with concurrent execution does not reproduce on the fork you sent, but there is another issue with double processing the same message (even after offset commit)
|
Closing this issue due to the release of KafkaJS 1.7.0 |
Describe the bug
When an exception in onBatch is being thrown, as mentioned in #1064 the error is swallowed, but the loop with batches still executes.
Concurrent should handle the problem by calling clear, but the promise is resolved by
unlockWithError
To Reproduce
Expected behavior
Second message processes, heartbeat starts, fails with "rebalancing error", rebalance starts, no messages being processed till the end of the rebalance.
Observed behavior
Second message processes, heartbeat starts, fails with "rebalancing error", messages from the second partition starts to process in parallel to rebalance, rebalance starts
Logs
Environment:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: