Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support for closing a consumer without auto-committing offsets
See original GitHub issueWhen I destroy a consumer I want to be able to call close() on it so it is removed from the consumer group (without having to wait for the session timeout).
Calling close triggers a offset commit when using auto-commit, which assumes you have finished processing all messages you have retrieved via poll() or the iterator. However, if you are closing the consumer due to an error or interrupt you may not have finished processing the last message(s).
There doesn’t seem to be a way to close the consumer without committing offsets when using auto-commit.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I put up a small PR to address this. I agree that it diverges from the java client implementation and that autocommit-on-close is generally the intended use case. But hey we’re pythonistas, and adding an optional kwarg doesn’t seem too bad. Thoughts?
Fixed in #1031