-
Notifications
You must be signed in to change notification settings - Fork 121
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
Transactional Producer instance gets timeout getting commit lock while second instance starts #803
Comments
Hi @PatrickChauveau - thanks for report. Is the issue consistently reproducible? Would it be possible for you to create a reproducible example ? Either as a simple app or integration test - as that would help a lot to identify potential bug. |
Yep - i have found a race condition - it is between commitOffsets on normal work and commitOffsets due to partition revocation. |
Glad you found a clue! It does not appear every time, might be 50% occurrences. We set in place health endpoint associated with kubernetes liveness probe to thwart the issue (it needs sometimes 2 or 3 restarts to stabilize). ParallelEosStreamProcessor.getFailureCause() helped a lot for this! Failure message: Error from poll control thread: There is a newer producer with the same transactionalId which fences the current one. |
Hi,
While instance A is consuming/producing records from topic full of records, instance B is started, the following sequence takes place:
The used configuration is:
The text was updated successfully, but these errors were encountered: